I think you will find writing code in .NET really cool, its a great IDE, and the framework is very powerful.
As for deployment, well, don’t count your chickens just yet! MS have made a huge effort to make it smoother, but it’s still a PITA, – when we are talking COM/.Net interop. VSTO is much better than it was.
]]>Ok, j/k, I had never even seen the Project Properties > Publish tab before. Very cool, thanks for pointing that out. I’ll have to try to play with that some time.
If things get more complicated, you might have to add a Setup Project to your solution. But I’m going to try your Project Properties approach at some point, it looks like it’s great for handling a basic install.
]]>LOL! I had a hard time figuring out where the completed build went. I didn’t realize that there was a bin\release folder that takes the completed version. I’ll have to re-compile it and upload it later.
So, to answer your question, I did it by accident. To mess yours up too, you’d go into the Project properties –> Publish tab, and set your directory. I just happened to set it to something within my documents folder. Doh!
]]>FYI the full .NET 3.5 SP1 package is around 250 MB, but I assume that is if you didn’t have .NET on your computer at all.
]]>Welcome to the .NET club.
Deployment of a straight .NET application is really simple, as you found. I don’t have VSTO experience, but VSTO deployment used to be very complicated, and may still be, I don’t know. I’m hoping it is not to bad by the time I am ready to use it.
In between can be deploying an add-in for an MS Office app like Excel. It’s not generally too bad, but your add-in is .NET, but has to be exposed to, and registered for, COM. This is normally handled by the Setup Project for you, but complex cases can require some manual tweaking and some headaches until you know what you are doing.
By the way, why didn’t you install into the Program Files directory? It looks like you installed into a temporary folder, I guess? (Actually I don’t even know how you did that… how did you do that?)
Anyway, a great first foray into .NET, Ken. Very cool…
Mike
]]>Hmm… fireworks… that would be interesting…
]]>As for excitement, you need Solitaire like fireworks for correct answers.
]]>