This is a good overview of what a Smart Client is: http://msdn.microsoft.com/en-us/library/ms998468.aspx[^] This is a starter how-to: Click Once Deployment Technique[^] This article is missing one huge step though - Signing your app with a certificate and running the MAGE.EXE command on the deployment server. It'll work in VS, but then when you move it to a real web server, you have to include the certificate file and then run the MAGE commands to "certify" it on that machine. For instance; Say your application is called "BobsApplication" You would copy up the deployment files that VS outputs AND the certificate file (.pfx) that you need to generate under the "signing" tab. (in the Project->Properties->Signing tab), and the MAGE.EXE program up to your web server. You can put the cert. file and mage.exe in the same folder as your application. Then run the following MAGE commands at the DOS command line: mage.exe -Update BobsApplication.application -pu http://YourServerName/BobsApp/BobsApplication.application mage.exe -sign BobsApplication.application -cf BobsApplication_TemporaryKey.pfx ** Where BobsApplication_TemporaryKey.pfx is the certificate file that you generated under the Project->Properties->Signing tab. I also assumed you created an aliased folder in IIS call BobsApp in the first mage command. MAGE.EXE comes with Visual Studio, you can find it in the SDK folder (C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin) Then, to Run your application, you would go to the browser and type: http://YourServerName/BobsApp/BobsApplication.application I would also search Google for something like: "Building your first ClickOnce application" or "Building your first SmartClient application" Hope that helps!

Why not just make it a Click Once "Smart Client"? Then you can keep it a windows application, but deploy it from the web like a Java Applet. You'll probably need very little code changes, it's more of a deployment option really and simple to implement. Unless you have a customer willing to finance the effort, it's probably not worth the massive amount of coding you'll need to do. You can do smart client in a day. The beauty of Smart Client apps is that you have a single install location (on the web server) to keep up to date. When the user clicks the icon, it automatically goes out to check for a new version and downloads it before starting up the app. It's really best of both worlds...

I don't intend to be mean sounding, but honestly, he sounds like a fool. Who would walk into a new job and for no good reason say, re-write everything, or switch languages so that now we have two languages to support? What's the business benefit? Makes no sense. I can't imagine what it is, but if there is one very specific thing you can't do with VB.NET that you can in C#, just write that one very specific thing in C# and move on. Re-writing working code just for sake of switching languages not only offers zero benefit to the business, but it costs the business time and money. I would fire that guy before he even started just for suggesting it, it's irresponsible. I write code and I manage large development projects and what I've found is, ask yourself a simple question when making decisions like this... could I stand up in a board meeting and explain why this decision was made and how it will ultimately benefit the company? If not, don't do it.

I know. It's the oldest debate in programming history. I don't even know why I started the conversation. I must have been in a bad mood that day when I saw that post. It is quite annoying though. I've seen things done in VB.NET that are incredible. I relented to the C++ guy because he showed me proof, but I have yet to see something similar for C#.

Why did I even try to have an intelligent conversation on this board? I'm surrounded by neophytes. :sigh: Tell me why you think that? Do you have a good reason, or are you just being prejudice to your language of choice?

There are Prom Queens here?! Sweeeet. Ok, or "Prom Kings" for the ladies. (and dude's who are into that kind of thing. Not that there's anything wrong with that...)

Ok, I'll give you that, I knew C++ was always better. :-> I programmed in C++ back in 90' for 3 years when it took 100 lines of code just to show a blank window. I should have been more specific and said specifically C# vs. VB.NET. What about that? Is it true for C# vs. VB.NET as well? Hey, I'm open-minded as long as it can be proven. If it's true, it's true...

I just read a post where someone was trying to decide to write a new application in C++ or C# and commented on how some lame team member suggested VB.NET. Don't you people get it yet? It doesn't matter what language you program in .NET! I've written over a million lines of code across a few applications since 2001... and, oh my god, in VB.NET. I've never been limited in any way, and they are incredibly powerful systems. People who make comments to make themselves feel superior are whiners, and wannabee's. People who ARE superior take home the prom queen. Matt