It looks like you're new here. Sign in or register to get started.
you don't need to learn C#...it COULD be useful to know it for the future, but i cannot predict the future...
In nav 2009SP1 you will also be able to create additional components (client extensibility) which requires .NET skill to create them...
if you have time to do it, then do it...it's useful!
(personally, i don't know it)
Nav experts blogs?view the signature of MVP/MSFT members of mibuso...usually they put their blog link there...
According to Microsoft's statement of direction C/AL will be phased out on the NAV 2013 release and switch to a completely .NET development environment. Personally, I think you should learn it now if you're going to continue with NAV as it can only make you more valuable down the line. You could also consider learning Sharepoint for the 2011 release, but .NET and C# seem way more valuable.
Of course this is all assuming Microsoft can stick to a schedule :whistle:
In NAV 2009 you can use .net and C#/Vb/? for automation objects and for applications, which interacts with NAV through web services or other means. These would all be on the side of NAV.
In NAV 2009SP1 we add the ability to create your own custom controls in .net and embed them into the RTC as first class citizens.
You cannot however write Business Logic in C# today. Personally - I am a C# developer, learning C/AL code... :-)
Also note that NAV 2009 actually converts your C/AL code to C# and compiles it on the service tier, where the application is running managaed code.
As the statement of directions says we are working on changing the programming environment to .net, but it is important to also state that we will NOT just give you a Visual Studio solution and tell you to go party. NAV will keep you in a simple world, where you concentrate on writing the application and the Business Logic and not focus on all the surrounding things. That said we also want to enable people with VS skills to do more.
So Yes, .net skills are great to learn, but nothing goes without C/AL skills today. I actually think that the hardest thing to learn isn't the syntax of C/AL or C# - it is the functionality of the application and where to do what.