If your only concern is that VC++ 2005 won't compile your VC++ 2003 MC++
code, don't worry about that. Using the /clr:oldsyntax switch, you'll be
able to compile MC++ code with the new environment. It's a different
issue entirely that you may not want to continue the development in
MC++, because the new syntax is so much better.
The question is if you'll be able to mix old and new managed C++ syntax
within the same project (without having to separate old and new code in
different DLLs). I can't answer that for sure, but I have a feeling that
you can't. For example, how would you #include MC++ declarations from
C++/CLI? I believe if you want to mix the two languages, you pretty much
have to separate them in two different .NET assemblies. Someone who
knows better, please correct me if I'm wrong.
Also, I wonder if the designer in VC++ 2005 will work with code
generated by the VC++ 2003 designer. Because it's one thing to compile
an existing code, and another to continue developing it.
You may want to know that VC++ 2005 Beta 2 has a "go-live" license, so
you are legally allowed to distribute software developed with Beta 2.
It's a beta, nonetheless, with its own issues and bugs, lack of
guarantees. Many 3rd party .NET components, designers, VS add-ons, etc.
don't work with VC++ 2005 yet (in fact, I can hardly find anything that
works with 2005). I can't even find a book about 2005 or the new C++/CLI
syntax yet. Still, it's possible to do some serious development with
Beta 2. You certainly run a lot of risk with Beta 2 if your deadline is
1/1. The final product will be barely out by that time, and I can only
hope it won't be delayed further.
The .NET framework 2 is slightly different from 1.x, so it's not just
the C++ syntax that's different, it's also the underlying libraries.
There are some breaking changes from 1.x to 2.0 that you have to deal
with. I definitely have .NET DLLs that only work in 1.x and not with 2.0.
I think I'm pretty much in your shoes, and I can assure you we're not
alone. I'm not coming from MFC, but may be going to VC++ 2005 like you,
doing everything possible to skip 2003.
Tom
Eddie Paz wrote:
I have a program written in MFC. I'm at the point where I need to start
working on the major release (tons of new features needed - new fiscal year
budget and all-).
I'm looking into vc++.net since I figure that I need to buy the bullet
already and get into the .net thing. I'm concerned, however, with the syntax
change in Whidbey. I feel that if I start coding now, I'm going to have to
update all my "old" syntax to the new. My deadline is 1/1/06.
Should I do it in MFC and save myself some grief or will the current syntax
be no problem with the new syntax? Any advice will be appreciate it. Thanks!