Installers

Deploying a finished application to a Windows Mobile Device

So you’ve gotten your toy all prepped and ready to rock.  Great.  You can test out the application on as I outlined on the physical device but the issue is as soon as you untether the device, BAM, the application exits. For me and the mass amounts of rocking requires an install for my device, so how do we do that?  MSDN has a nice write up for deploying Windows Mobile applications but I’ll walk through my deployment for you too. We’ll right click on the solution in the solution explorer or we can go to File->New->Project.  If...

Making ClickOnce less annoying.

After chatting with my installer expert, he mentioned ClickOnce does have a ton of options to make this work properly. MSDN, what would .Net developers do without you. http://msdn.microsoft.com/en-us/library/s22azw1e(VS.80).aspx

ClickOnce and updating

ClickOnce has some pretty nice advantages.  All I need to do is upload the new files and it magically updates the clients. But it has a problem, every start up, this pops up.  It is super annoying. I have a project installer with an old school installer that seems to have the auto-updating ability too. If I migrate from the ClickOnce, I have to figure out also how to do a seamless transition.  The ToDo project already has end users.  Of which, today, got a nice present.  I added in...

ClickOnce!

I spent a bit attempting to figure out how to do a ClickOnce installer for ToDo.  I was shocked to see where it was actually.  I had to ask Martin Schray where since he created a how-to video on the “normal” installer. So if you want to create a ClickOnce application, follow along. Open up Visual Studio and whatever solution makes you feel good inside about. Be sure the project you want deployed is selected in your solution window Go to Build –>...