Thread: program made in vb.net performance

Hello.

No, not really. I mean, it can't be as fast as a native application, but the only real bottlenecks and slowdowns I experienced were design errors (made by me ).

Though, I'd say that everything that runs XP can run .NET...whatever application it is.

Bobby

@Bobby: is a program in design time improves when it gets package and deployed? sorry i have so many questions about this its just that i want to hear from people with experience in .net. thanks!

Not necessarily, I mean, at Design-Time their's the debugger attached and possible Debug-Output is slowing down the execution (which get's dumped when you Build it for the release). If you want to test the performance, then the best way would be to just take it to test drive outside the IDE or even within a virtual machine.

I've never much cared about performance of my program until it was needed. There are some rules which you can stick to:
* To concatenate large strings (f.e. within a Loop) use a Stringbuilder (System.Text)
* Always declare variables outside of Loops
* At very large collections use a normal For Loop instead of a For Each (one variable declaration less)
* Try to avoid unnecessary calls and exceptions

Bobby

ok.. thanks for the words of wisdom bobby!

Originally Posted by Robert_Zenz

* Always declare variables outside of Loops

Not necessary. The compiler will move the declare out of the loop in the real program. Declare your variables as close to where you will use them as possible and keep their scopes small for more readable, logical code

* At very large collections use a normal For Loop instead of a For Each (one variable declaration less)

Using For Each sets up an enumeration which can be many hundreds of times faster at accessing a collection than a positional based indexer (Linked list for example must count 99 items before it can return you the hundredth, a LinkedList of 100 items iterated using a positional indexer must perform 5000 skips to return all items: don't do it).
Do not advocate positional indexing purely on a variable declaration saving (nanoseconds)

* Try to avoid unnecessary calls

Again, nanoseconds, and youre advocating making code one huge long unreadable procedure for the sake of minor inlining performance (which the compiler will perform if it feels the need) gain. It's not worth it: readable code first!

Originally Posted by thejeraldo

any guys right here ever experience having their programs made in vb.net run slow on the computer it was deployed at?

No, but there could be a load of crap on that computer

what are the system requirements to run a program made in vb.net with framework 3.5?

My sat nav runs .net programs very well, and that has something like a 200mhz processor and 40mb of ram

is it a simple program or a large program (eg with database)

doesnt really matter

thanks cjard. its a great advice to consider code management if it only cost you nano seconds. and thanks for saying that a 200mhz processor and 40mb computer can run .net apps well. now i can feel a little lighter with this project im making. thanks a lot. everybody has been helpful in this forum.

Originally Posted by thejeraldo

what are the system requirements to run a program made in vb.net with framework 3.5?

from Download details: .NET Framework 3.5

System Requirements

* Supported Operating Systems: Windows Server 2003; Windows Server 2008; Windows Vista; Windows XP
* Processor: 400 MHz Pentium processor or equivalent (Minimum); 1GHz Pentium processor or equivalent (Recommended)
* RAM:96 MB (Minimum); 256 MB (Recommended)
* Hard Disk: Up to 500 MB of available space may be required
* CD or DVD Drive: Not required
* Display: 800 x 600, 256 colors (Minimum); 1024 x 768 high color, 32-bit (Recommended)

Originally Posted by thejeraldo

is it a simple program or a large program (eg with database)

Hardware and Software Requirements for Installing SQL Server 2008
Compact Hardware and Software Requirements