C/SIDE skills will be needed for at least 5 years after the next release of Navision, and if you are working for a solution center even longer after that. For as long as there are companies that run Navision in its current incarnation, there will be work for C/SIDE skilled people.
Regardless, there is no real need to know much of SQL, unless you get involved in the more advanced performance trouble shooting jobs where databases grow big or where functionality needs anhancing.
I'm afraid I can't say much about how much .NET will play a role in the next Navision version. However, if you look at what is coming down in the next Axapta, and what has just been released in the next GP, you will see where they are going with Dynamics. Of course .NET will play a bigger role, because that is the Microsoft flagship platform.
Also, go to the Microsoft website and search for the upcoming products, about their vision on the software architecture. See how much they emphasise connecting applications, and you will get a vague idea of what they are thinking of.
Also, I am curious how to move a non-OO language into .NET. Sound quite impossible.
That would not be hard to do at all.
You could use a flat namespace for everything (or no namespace art all), and treat all procedures in a code module like they were Public Shared Subs or Functions in VB. That way there is no need to instantiate any object and your OO runtime behaves just like a non OO runtime. Unlike what many people think, you don't *have* to use OO in .Net. Off course you lose most of the power of .Net if you don't use it, but it couldn't be more cripled than C/SIDE already is.
Yeah, I know I my frequent complaints make me look like being a complete asshole, but just try one project here, where people expect 300% boost of productivity when buying Navi and are quite pissed if they get -10% (and that's already to my effort, with standard it would be -60%). You know once I did a project in Denmark and another one in Austria and was quite surprised how users accept every kind clumsy, bad, unproductive, but "flexible" solution to problems. They sometimes even demand to leave the standard, flexible and bad functionality as it is and don't make it into something that works... completely amazed me. You know, places and expectations are just... different.
Do It Yourself is they key. Standard code might work - your code surely works.
I recently went to the GP 9.0 launch and it looks like they're shooting for a 2008/2009 launch of Project Green. In GP 9.0 you can *almost* develop completely in .NET. Almost makes me want to switch teams again. :shock:
In GP 9.0, Dexterity is still their main platform, but you can use .NET to tap into GP. You have new GP application templates in .NET with a set of namespaces/objects that link into a GP Application Instance. This means you can access Core GP windows from a .NET application. They also have objects that look exactly like GP Windows/Controls so you can create GP windows from within .NET, but you can also use other ActiveX controls such as IE.
I haven't seen anything for the next version of Navision but I can only assume that it will run along the same lines.
I recently went to the GP 9.0 launch and it looks like they're shooting for a 2008/2009 launch of Project Green. In GP 9.0 you can *almost* develop completely in .NET. Almost makes me want to switch teams again. :shock:
In GP 9.0, Dexterity is still their main platform, but you can use .NET to tap into GP. You have new GP application templates in .NET with a set of namespaces/objects that link into a GP Application Instance. This means you can access Core GP windows from a .NET application. They also have objects that look exactly like GP Windows/Controls so you can create GP windows from within .NET, but you can also use other ActiveX controls such as IE.
I haven't seen anything for the next version of Navision but I can only assume that it will run along the same lines.
Didn't you just describe the next version of Navision, won't it most likely be the great plain project green program, and a set of tools to migrate Navision users to it. Before then there will be a Navision 5. that will change the look and feel a little more toward the project green.
Yes this is internal Microsoft confidential information. Just about everything in this document is under NDA. Someone at Microsoft is going to get in trouble for making this available to the public. On the other hand... it IS a publicly available website, so anybody that speaks Dutch can read it.
Comments
My blog
The move to .net is unavoidable, but will take years.
Regardless, there is no real need to know much of SQL, unless you get involved in the more advanced performance trouble shooting jobs where databases grow big or where functionality needs anhancing.
I'm afraid I can't say much about how much .NET will play a role in the next Navision version. However, if you look at what is coming down in the next Axapta, and what has just been released in the next GP, you will see where they are going with Dynamics. Of course .NET will play a bigger role, because that is the Microsoft flagship platform.
Also, go to the Microsoft website and search for the upcoming products, about their vision on the software architecture. See how much they emphasise connecting applications, and you will get a vague idea of what they are thinking of.
RIS Plus, LLC
Do It Yourself is they key. Standard code might work - your code surely works.
RIS Plus, LLC
You could use a flat namespace for everything (or no namespace art all), and treat all procedures in a code module like they were Public Shared Subs or Functions in VB. That way there is no need to instantiate any object and your OO runtime behaves just like a non OO runtime. Unlike what many people think, you don't *have* to use OO in .Net. Off course you lose most of the power of .Net if you don't use it, but it couldn't be more cripled than C/SIDE already is.
Mabye he will make navision more simple...
http://www.mibuso.com/forum/viewtopic.php?t=7955
Sorry; friday afternoon :-#
Do It Yourself is they key. Standard code might work - your code surely works.
Do It Yourself is they key. Standard code might work - your code surely works.
Do It Yourself is they key. Standard code might work - your code surely works.
RIS Plus, LLC
Do It Yourself is they key. Standard code might work - your code surely works.
In GP 9.0, Dexterity is still their main platform, but you can use .NET to tap into GP. You have new GP application templates in .NET with a set of namespaces/objects that link into a GP Application Instance. This means you can access Core GP windows from a .NET application. They also have objects that look exactly like GP Windows/Controls so you can create GP windows from within .NET, but you can also use other ActiveX controls such as IE.
I haven't seen anything for the next version of Navision but I can only assume that it will run along the same lines.
But I hate the idea of migrating to GP, I like thinking the other way around.
RIS Plus, LLC
We won't tell :-# :-$
http://www.BiloBeauty.com
http://www.autismspeaks.org
RIS Plus, LLC
(check out 2 first links when google-ing on "Navision Corsica")
Bruno
http://blogs.ittoolbox.com/erp/smb
One of the interesting translated pieces is:
"On the market Navision 4.0 bring in October 2004 show our continuing involvement for providing terrible solutions"
I assume terrible was not the meaning intended....
http://mibuso.com/blogs/davidmachanick/
Please beware of the fact that most of the info on the internat are roumours that are not based on facts.
People who know about this are not allowed to say much. :-#
that is for the web page
file http://download.microsoft.com/download/ ... -_2005.pdf
thnis is for the pdf
http://mibuso.com/blogs/davidmachanick/
The first: In future the C/AL (in easy modified form) will be implemented in .net
the second: the programming in Navision is with an (now available, C# ... VB) language of .net
In my oppinion, they will use the first alternative
Regards
I am very sorry but I don't think is it appropriate if I translate this.
RIS Plus, LLC