Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / November 2005

Tip: Looking for answers? Try searching our database.

VC++ 2003 or VC++2005.Net for Native Code Support?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
James S - 06 Nov 2005 19:15 GMT
Hi

I've been porting a project to .Net that has several segments of code that I
would like to keep as native code in wrappers. I've been using VS2003 and
VC++ to create mixed dlls that I then can used from C#.

I see that the new 2005 version has a new and significantly different syntax
and way of doing things with native code, and was wondering if anyone has
any experience of using the new version to perform this sort of task. And
more importantly, if they would recommend using the 2005 version over the
2003 version. I've seen reports that it can run faster, and does not have
the dll load lock bug etc. I've not been able to see anything on the new
versions reliabilty and ease of use, etc.

Any comments on this, or links to anywhere this is discussed would be most
appreciated. I've tried searching for this kind of thing, but most the time
it seems to just take me back to the MSDN material.

Many thanks

James
Carl Daniel [VC++ MVP] - 06 Nov 2005 21:03 GMT
> Hi
>
[quoted text clipped - 13 lines]
> most appreciated. I've tried searching for this kind of thing, but
> most the time it seems to just take me back to the MSDN material.

My $0.02 worth -

Use 2005 if you have the choice.

-cd
Marcus Heege - 06 Nov 2005 21:40 GMT
The important question is: Is it acceptable to implement your application so
that it can only run with v 2.0 of .NET.

If yes, then VS2005 is the only sensible option IMO. The old managed
extension syntax is not only ugly, it is a dead end syntax. It is still
possible to compile the old syntax with VS 2005, but due to the new syntax
it will significantly loose relevance.

Marcus Heege

> Hi
>
[quoted text clipped - 17 lines]
>
> James

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.