Reply to thread

Message

You wouldn't have these problems if you developed an MSI [Windows Installer] package and a bootstrap installer exe for your program, which could have an installer pre-condition to check the requirements of the system. Of course, few builds an MSI package for deploying an application(s). It is beneficial if your IT department has a way to "push" updates to machines.

However, we live in the ClickOnce [.NET framework 2.0+] world, where you could just publish the stuff to a web site and have preconditions which can check a whole bunch of requirements. It also solves the headache of going to each users machine and updating your application, cause the process becomes seemless.

A reply of whether to use VB.NET or C#.NET. You could use any language that you find comfortable. C# is considered more of a "power" language because it can have unmanaged code and has more of the C++/Java style syntax. On the other hand, I would feel upset switching from VB6 to VB.NET. Microsoft changed and introduced a whole bunch of new concepts that are radical to the language eg. Operator Overloading, Namespaces, Multithreading, Array Indexing, etc.

Personally, I feel the jump from C++/Java to C# isn't all that big compared to the jump from VB6 to VB.NET.

<blockquote data-quote="bobbychopra" data-source="post: 11311" data-attributes="member: 517">You wouldn&#039;t have these problems if you developed an MSI [Windows Installer] package and a bootstrap installer exe for your program, which could have an installer pre-condition to check the requirements of the system. Of course, few builds an MSI package for deploying an application(s). It is beneficial if your IT department has a way to &quot;push&quot; updates to machines. However, we live in the ClickOnce [.NET framework 2.0+] world, where you could just publish the stuff to a web site and have preconditions which can check a whole bunch of requirements. It also solves the headache of going to each users machine and updating your application, cause the process becomes seemless. A reply of whether to use VB.NET or C#.NET. You could use any language that you find comfortable. C# is considered more of a &quot;power&quot; language because it can have unmanaged code and has more of the C++/Java style syntax. On the other hand, I would feel upset switching from VB6 to VB.NET. Microsoft changed and introduced&nbsp; a whole bunch of new concepts that are radical to the language eg. Operator Overloading, Namespaces, Multithreading, Array Indexing, etc. Personally, I feel the jump from C++/Java to C# isn&#039;t all that big compared to the jump from VB6 to VB.NET.</blockquote>

[QUOTE="bobbychopra, post: 11311, member: 517"] You wouldn't have these problems if you developed an MSI [Windows Installer] package and a bootstrap installer exe for your program, which could have an installer pre-condition to check the requirements of the system. Of course, few builds an MSI package for deploying an application(s). It is beneficial if your IT department has a way to "push" updates to machines. However, we live in the ClickOnce [.NET framework 2.0+] world, where you could just publish the stuff to a web site and have preconditions which can check a whole bunch of requirements. It also solves the headache of going to each users machine and updating your application, cause the process becomes seemless. A reply of whether to use VB.NET or C#.NET. You could use any language that you find comfortable. C# is considered more of a "power" language because it can have unmanaged code and has more of the C++/Java style syntax. On the other hand, I would feel upset switching from VB6 to VB.NET. Microsoft changed and introduced a whole bunch of new concepts that are radical to the language eg. Operator Overloading, Namespaces, Multithreading, Array Indexing, etc. Personally, I feel the jump from C++/Java to C# isn't all that big compared to the jump from VB6 to VB.NET. [/QUOTE]

Verification