Exetools  

Go Back   Exetools > General > General Discussion

Notices

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #6  
Old 01-30-2005, 17:12
ArC ArC is offline
VIP
 
Join Date: Jan 2003
Location: NTOSKRNL.EXE
Posts: 172
Rept. Given: 0
Rept. Rcvd 1 Time in 1 Post
Thanks Given: 5
Thanks Rcvd at 17 Times in 12 Posts
ArC Reputation: 1
Quote:
Originally Posted by joejoejoe
So do I just open up a project and set those settings and expect it to work. Is there any places where I have to say ... "no.. not .NET .... its Win32"?
If you convert a VC++ 6.0 project to VS .NET it is automatically configured to produce native Win32 apps.
If you create a completely new project you have to choose which type of project you want to create. If you decide to create a Visual C# project the output will be a .NET executable. A Visual C++ project will produce native Win32 apps whereas those projects can be configured to use the .NET framework, too. But even in that case it should still produce native apps.
Quote:
I had no trouble converting VS6 projects/workspaces to VS.NET2003 solutions except for the C++ language compliance issues.
Some time ago I compiled a project with VS .NET 2003 and I encountered an INTERNAL COMPILER ERROR. The same project compiles just fine with VC++ 6.0 + latest SP + Processor Pack.
Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT +8. The time now is 03:32.


Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX, chessgod101
( Since 1998 )