Posts Tagged ‘C#’
For almost 15 years ASP.NET has been one of the best web development technologies and many developers consider it to be the best offering from Microsoft. ASP.Net evolves to bring in better features and functionality, which helps businesses scale better. Each year developers see few new trends that enhances development and shortens the time-to-market the solution. Here we will discuss a few trends that will benefit both developers and businesses indulging in ASP.Net.
Let’s have a glimpse at it benefits.
Data Flow in One Direction – Properties are passed to component to render HTML tags. Component itself cannot change the property; instead, it requires a callback function to modify the property values.
Easy to Integrate – React can be simply integrated with other tools or frameworks like Jest, Angular.js or Backbone.js.
Xamarin is highly popular mobile development framework with the rule write-once-run-everywhere coding for three leading mobile platforms: Windows, Android and iOS. It empowers developers to write in a single language on a single code base for their app to reach over billions of smart devices irrespective of the platform. Xamarin delivers perfect look and feel of any given platform’s native UI with power-packed functionality and native app performance. Xamarin eliminates the need to manage separate development teams or having to choose one platform over another.
Following are few more benefits of Xamarin:
Xamarin uses the C# programming language
C# is capable of doing anything you could do in Java, Objective-C, and Swift – and it works on platforms that use any of these. Most applications can share 75% or more of their coding, helping to make development on multiple platforms easier than ever before. Many functions unique to each device are mapped at runtime to correspond to that specific device, resulting in an end-user experience that works the way they expect it to work.
Xamarin can import and convert existing code
Do you have existing Objective-C or Java code? Xamarin uses an automatic binding generator to match code like custom controls and frameworks to your new app, and a little bit of testing is usually enough to fix any glitches that occur. By importing your existing code, you can hit the ground running and reduce the time it will take to roll out your improved app.
Xamarin offers same-day support for new OS releases
One of the biggest problems with apps is updating them when a new operating system comes out. These changes can cause major disruptions in the way some functions work, but this particular developer has been able to offer same-day updates that allow you to start taking advantage of new features and capabilities. These updates also mean that you can deal with any major disruptions to your app and get it back up and running if anyone was broken – your business can’t afford to have its tools stuck in limbo, and working with a company offering active support is one of the best ways of ensuring your investment won’t be lost at a crucial time.
Elasticsearch is the most popular enterprise search engine followed by Apache Solr based on Lucene. It provides a distributed, multitenant-capable full-text search engine with an HTTP web interface and schema-free JSON documents. Elastic search was first released in February 2010, and is a free and open source distributed inverted index created by Shay Banon. It is developed in Java, so it is a cross-platform.
Below you can find major highlights of Elastic Search:
Real-Time Data Analysis – All data is immediately made available for search and analytics.
Distributed approach – Indices can be divided into shards, with each shard able to have any number of replicas. Routing and rebalancing operations are done automatically when new documents are added.
Multi-Tenancy – Multiple indices can be maintained by single cluster and can execute queries individually or as a group. Also, maintain alias of indices and keep them updated.
Full-Text Search – Elastic Search implements a lot of features: customized splitting text into words, customized stemming, facetted search, and more. Powerful, developer-friendly query API supports multilingual search, geolocation, contextual did-you-mean suggestions, autocomplete, and result snippets.
Easy-To-Use RESTful API – Elastic Search is API driven; actions can be performed using a simple Restful API.
Open Source – Elasticsearch is available freely, under the most adoptable and trusted open source license of Apache 2.
In addition, the Microservices, Azure, and AngularJS are also trending in Asp .Net. Nowadays, enterprise applications are in high demand, and these tools are playing a key role to hit the ground and running.
Thanks for reading!
Business Development Manager
Professional Software Development
We are often asked about which iOS game engine to use. It is believed that most companies are looking for a free game engine so here is a comparison of the different open source iPhone game engines that actually have apps out there. Also these game engines now support the iPad.
The Sparrow Framework is a very lightweight 2D game engine created in Objective-C.
It was built from ground up for iPhone, iPad and iPod Touch. You can easily integrate it with your existing UIKit apps, access all iOS APIs directly and benefit from native performance.
If you have already worked with Adobe Flash or Starling, you will feel right at home: Sparrow uses the same concepts and naming schemes. Even if you’re coming from a different background, you’ll get the hang of it quickly, because everything is designed to be as intuitive and easy to use as possible.
The game framework includes all the necessary features you’d require for creating a basic 2D game such as easy animation, and a sound engine.
The Cocos2D iPhone game engine is a port of a game engine originally created in Python and converted to iPhone Objective-C. As you can tell from the name, Cocos2D is designed for 2D games, that being said, although the engine is in a 2D world, the engine includes a growing collection of high quality 3D special effects. Cocos2D has also been released on the Mac so you can ease the release on 2 platforms.
Cocos2D is the first engine to check out, while many may be turned off by the engine not supporting a 3d world, if you look at most of the top iPhone games the gameplay is 2D, in fact the iPhone’s touch screen controls can make it difficult to operate in a 3D world.
The engine provides more examples than any of the other engines out there because of the large community.
iSGL3D (iOS Scene Graph Library) is a 3D framework for the iPhone, iPad and iPod Touch written in Objective-C, enabling the creativity of developers to flourish in a 3D world without the complexities of OpenGL.
With its rich set of features, iSGL3D provides the necessary tools to develop 3D applications in an incredibly short time frame, even with a minimum of experience in 3D graphics. The principal behind iSGL3D is to make construction and manipulation of 3D scenes as simple as possible for a developer.
With a single line of code you can add a 3D object whether it is a simple primitive, a sprite (or particle) or your own imported asset. Properties on these objects allow you to modify their appearance, position, rotation and more very simply. You can add containers too to group objects and manipulate them together. In a short period of time you can build up a complex 3D scene.
The Moai SDK is an open source 2D game engine. It designed more for people who know what they’re doing. While it includes the ability to start developing a game immediately from a downloadable binary, it only supports using the FreeGLUT library on the desktop. It is designed in such a way that it expects the developer to be able to create the windowing system themselves.
The main language used with Moai is Lua. Most of the time you shouldn’t need to use C++ to extend the base engine, but the capability to do so is there. The documentation for the Lua codebase is kind of weak however, so you should be ready to do some searching to find out how to use various capabilities. You can create your games with Moai on both Windows (Visual Studio) and Mac (Xcode). In order to
submit your games to the iOS app store you will need to do so with a Mac.
The Oolong Engine is written in C++ with some help from Objective-C. It will help you to create new games and port existing games to the iPhone, the iPod touch and the iPad.
Oolong provides support for a wide variety of features and provides excellent performance.
Haxe is a multi-platform language that most notably compiles to SWF and has been used in many Flash games.
Galaxy Game Engine
The Galaxy Game Engine is a very promising engine with an extensive feature set. This is a BSD licensed 3D engine that includes some very useful tools such as a level editor, terrain editor, model viewer, particle editor, and shader IDE.
Sure, we may make this list longer, but let me stop here. The most important thing, which I’d like to notice, is that you should select the engine which fits your project needs and suits your purposes in the best way.
And what do you think? To what engine would you give your preference?
Feel free to share with us your thoughts!
Over the years dynamic languages such as Python and Ruby have become cherished by startups. As for .Net it is more rarely heard to be used by startups. That’s interesting indeed, because this platform is definitely bigger than most of the popular ones.
So I wonder why a platform as widely adopted and supported as .NET isn’t more visible in startup culture. Let’s try figuring out the main arguments in favor and against making .Net a startup technical choice.
1. Community culture
Some people say the main reason is the culture of the .NET community itself, not anything specific to the platform. Being centered mostly around the needs of enterprise market .NET developers’ concerns are often regarding supporting legacy systems, building enterprise architectures, large systems for supporting business processes. This implies solving problems which are not so relevant for startups at least at their initial point.
As for members of the startup community, they fuss over different issues – concurrency, experience design, supporting multiple clients and browsers, etc.
As a result the startup community and the .NET community don’t overlap as much as they do for other technologies. That’s why startup founders don’t get much exposure to .Net and don’t think of it as an applicable tool for their purposes. The same way many .Net developers who want to work for hot startups don’t have as many opportunities to do so unless they abandon the platform for a more startup-friendly one or start a company themselves.
So platform doesn’t always dictate its use – that’s people who make the choice. Enterprise and startups aren’t mutually exclusive – they’re just different stages in the evolution of software, and there’s no reason why the startup community shouldn’t look at .NET as an attractive starting point for a new business.
2. Startup tech compatibility
A startup is a risky venture with no guarantee of success. So tech startups seek advantages in order to succeed. Hence startups take what big enterprises consider risky bets on technology. This objective can be achieved by using technology that is popular in startup environment.
Many features of .NET, facilitating the productivity of big companies, are not always useful to startups. There is too much choice of implementation methods. If anything, web startups are looking to have this choice taken away – their technology choices come from the subset that is built for the web.
Also it is said that innovation is quicker with other ecosystems which have a bigger set of libraries and tools. As for .Net there are a few open source projects however most of them are pretty much an implementation of concepts that have already been implemented for a while in the Java world, for example.
3. Open source vs proprietary
Although many startups don’t mind paying for tools and services, most of them still pick things based on cost. For a long time the “enterprise” level tools, services, databases, etc were hardly affordable by startups. That’s why startups adopt so much open source.
It’s also hard to justify the use of proprietary software from a business perspective. If you want to be acquired it is wise to develop your product using an open stack rather than Microsoft’s.
However luckily for many startups Microsoft saw a huge value in giving their stuff away to startups and startups have benefited greatly. Microsoft has been running their Bizspark program for several years, which eliminates most of the startup costs normally associated with employing a .NET framework. To get into the BizSpark program you just need to get checked by BizSpark team if your startup is eligible (developing a real product). Then you’ll get free licenses to basically every product they make, including SQL Server, and a free MSDN gold subscription, for 3 years. They figure 3 years is long enough for you to get going so after that they want you to pay for new licenses. The great part is that they let you keep the licenses you’re already using. So Microsoft has basically taken the cost factor completely out of the equation for new startups.
4. Velocity vs performance
Some people say that it’s all about the velocity. If you agree with an assumption that a startup goal is to find a niche vs build a product, then the goal of a startup is to learn about the market, customers, and product needs as quickly as possible. Python, Js, Ruby, etc allow you to iterate quickly without a lot of infrastructure and boilerplate. However a company that has already has a market has a little different goal, for them the objective is to build a stable product that they can maintain.
Some people say that .Net is not suitable for quick changes. This is a pretty outdated view of C# these days, it’s actually fairly easy to write extremely terse code with. As an added bonus refactoring is so incredibly easy compared to JS, Ruby, Python, etc. that it’s ideal for rapidly switching directions in code as you can refactor so fearlessly without being slowed down by massive amounts of tests. Unfortunately what’s bad about .Net is the tooling and the supporting ecosystem.
Python is much better suited to quick prototypes that can be fleshed out into a reasonably reliable product without too many headaches. The key difference comes when you have to change features mid-stream. The lack of strict typing and interfaces means you can add, change, and remove features much quicker than C# for example. On top of that, you just write fewer actual lines of code to get the same thing done, although sometimes readability can suffer if you get too concise. There is a price to be paid with Python and Ruby though and performance is the biggest one.
5. Team and project size
The team and project size always matters. So when the solution is being built with a small team, then it is easier to use something like Python. Obviously the goal is to be fast to develop in and have a bunch of libraries to be used. On the other hand when building something with a big team, you feel like using something like C#. In this case it keeps it safe to develop in and easy to catch mistakes. Any optional documentation provided by a developer is incomplete. On the contrary the quality level of the available .Net documentation is outstanding.
However if the company is starting as very small at the initial point, it hopefully grows and builds up quite a sizeable codebase by some point. Python, JS & Ruby are fine for small programs but anything more than that and they become their own enemies because the programs they make are quite brittle.
The common opinion is that .Net scales well.So, if your startup does make it, you’ll probably have a much easier time scaling the .Net stack than you would with say Ruby or PHP.
Conclusion: it’s all about stereotyping
Eventually, I found different opinions on my question of .Net being not so popular with startups such as “platform lock-in,” “no open standards,” “licensing costs.” Sure, these are issues preventing many developers from adopting .NET in the startup space, but not enough to bar all of them from using it. Most of the arguments are just stereotypes that can be dispelled under closer examination.
All languages have strengths and weaknesses. For a startup, you need to do due-diligence and research what the right language to use for your idea will be because recoding in a different language can get costly.
So do you use .Net in your startup projects? Please share your feedback and experiences with us.