Jump to content


Photo

PRG- Which .net 2003?


  • Please log in to reply
4 replies to this topic

#1 Hymie the Control Robot

Hymie the Control Robot

    Sergeant

  • Forum Members
  • PipPipPip
  • 50 posts

Posted 03 May 2004 - 12:42 PM

Currently I'm using VC++ 6.0, but because of all the compiling problems with the devpack (even after conversion), I'm thinking of upgrading to .net 2003. I'm just wondering which version of .net 2003 is being used by most developers here? Is it the standard edition or the professional? I heard that the standard edition has serious optimization problems. Does anyone know if that's true?

Thanks everyone.

#2 mamutas

mamutas

    Colonel

  • Forum Members
  • PipPipPipPipPip
  • 1,067 posts

Posted 03 May 2004 - 04:00 PM

The project should be compatible between all version of .NET 2003 whether it is standard, pro or architect.
I did not hear about the optimization problems and google search did not yield anything useful. Do you have more info?
mamutas@sourceforge.net

#3 Hymie the Control Robot

Hymie the Control Robot

    Sergeant

  • Forum Members
  • PipPipPip
  • 50 posts

Posted 03 May 2004 - 05:17 PM

The project should be compatible between all version of .NET 2003 whether it is standard, pro or architect.
I did not hear about the optimization problems and google search did not yield anything useful. Do you have more info?

I've heard of this at work, but I couldn't find anything concrete other than some reviewers on Amazon.

http://www.amazon.ca...9800503-3898407

For them at least, the standard compiler was apparently slower than VC++ 6.0. But another reviewer said that the free VC++ toolkit has the compiler from the pro edition (which is true as far as I can tell), and increases the speed dramatically.

So this is probably nothing.

I just wanted to know if it makes any difference, since upgrading to standard is a lot cheaper than upgrading to professional. :)

#4 red knight

red knight

    Xenocide Project Leader

  • Xenocide Inactive
  • 3,310 posts

Posted 03 May 2004 - 09:45 PM

I heard that you just can get standard and copy the files of the free compiler to use the optimizing compiler... I dont see any reason while it cant be true, but I cannot assert it for sure.

Greetings
Red Knight
Sourceforge Nick: flois - Federico Andres Lois
Visit my blog at: flois.blogspot.com

Posted Image

Pookie cover me, I am going in.

#5 Hymie the Control Robot

Hymie the Control Robot

    Sergeant

  • Forum Members
  • PipPipPip
  • 50 posts

Posted 11 May 2004 - 11:14 PM

I heard that you just can get standard and copy the files of the free compiler to use the optimizing compiler... I dont see any reason while it cant be true, but I cannot assert it for sure.

Greetings
Red Knight

I just got VC++ .NET standard edition, and I'm afraid the problems seem to be true. I compiled OGRE again into VC7 binaries (interestingly enough, OGRE doesn't seem to need STLPort with .NET 2003 anymore), but the sample OGRE apps ran horribly! With the same resolution and rendering methods that I used with VC6 binaries, the frame rate for some of the samples became around 40 or 30 fps with the VC7 binaries, when they used to be around 200 fps! Loading time for the sample apps have also increased. Also, for the standard OGRE sample application's framelistener, the escape key is defined to close an app, but now it doesn't seem to work anymore. I still have to find out why.

I'm currently trying to use the compiler from the free .NET toolkit to see if the performance improves.