It's slow!!!

It's slow!!!

• Scott Michael

  Yes and no.

  VB 2005 executables are JIT (Just in Time) compiled at runtime, but it is possible to create a native version of the code that has been almost pre-compiled into native code which can potentially speed things up a little.

  A utility is provided to do this called NGEN and a web search on NGEN + VB.NET will reveal some interesting articles

  Here's one.

  http://visualbasic.about.com/od/usingvbnet/a/FWTools2.htm

  But you really need to understand how the underlying code is IL (Intermediate Language) and not native code and NGEN your code may not provide a tremendous improvement in performance.

  
  

• Michael McCormack - MS

  I mean by "long time" that it takes a few seconds to load my application which programed via VB2005.

  I'm with u that .NET Framework is too powerful.

  But on the other side there are some problems in NET Framework.

  And I use Windows XP SP2.

  Can I make my applications faster

  
  

• Peter_DK

  Where can I find RunOn8086Processor and Apple
  

• Devo-2K

  Gentlemen....

  As much as I cling to your every word, please stop kidding this customer.

  Hey spotty...

  I have a job for you....

  
  
  

• Rchard Ramsden

  I can't find System.Magic namespace.

  I use VB2005.

  
  

• zzamee

  What's LoadQuick

  And how can I set it to True

  
  

• jairo_jeremias

  I can't wait for the Apple = True setting: That MacOS sure looks pretty!
  
  

• Nick Ericson

  1. Live with it - that's not really a 'long' time - I though you mean't 30-60 seconds - for the first time loading of a .NET application.

  2. Use another language; C++ would be the way to go if speed is a problem.

  3. Get a faster computer.

  3. Set the LoadQuick flag to True.

  4. Break down your program so that it 'appears' faster. Don't load everything at once; just load what is needed. This is what the OS does - look what happens when you first access a web page in IIS.

  
  
  

• DanDare

  It's in the System.Magic namespace, along with the UseNoMemory setting and the NoCodeRequiredToWork flag. Also, the MakeMyLifeDifficult property is set true by default, and is unfortunately ReadOnly (this is actually a bug that may be fixed by the next service release). However, the MakeItDoWhatIWant setting can be set to either DoIt.Graphics or DoIt.Everything to override this setting. Most people have trouble finding these settings but usually get excellent results, after a period of time, without resorting to the Magic namespace.

  
  
  

• Xpyder

  Both the

  RunOn8086Processor and RunOnApple are compiler switches on the command line compiler. but these are only available on Beta versions of VB 2005.

   

   

  
  

• Sameer Bhangar

  Is that namespace contained in the DoEverything.dll

  
  

• byteshack

  Do those functions take into account the setting of the turbo button on the front of my machine and is this compatible with the RunOn8086Processor setting for the VB 2005 compiler.

  As I could use this feature to make my VB2005 application run on my original IBM PC and run quickly at that.

  
  

• Philip at Alpha Index

  I have VB2005 Professional Edition.

  Where can I find RunOn8086Processor and RunOnApple

  
  

• AmandaB

  What do you mean by 'long time' It's possible that, even though windows appears to have finished booting up, it hasn't - it's still loading and starting various services (e.g.SQLServer).

  Additionally, it may be that the .NET framework needs to load prior to your application loading. Did you try using a splash screen to see if that shows any quickly

  (p.s. dos and windows is 'faster' than Windows XP - it's all relative. VB6 applications may load 'faster', but .NET is much, much, more powerful).

  
  
  
• It's slow!!!