CODEWITHSUNDEEP
.netclickonce
user120242
user120242

Reputation: 15268

Moving to .NET Framework

We have an application that is being moved to .NET. One part of the application will be deployed using ClickOnce, SXS (registration-free COM to host ActiveX controls which may be ported later). This part is not as big a deal, as the environment is controlled. This will be a mostly "consulted" environment.

Another part is a mostly web-based (Internet Explorer specific) application. This part involves some VBScript, JavaScript, and just a couple of ActiveX controls.
This part really worries me. Especially because it's supposed to be usable by home users. It's already a mess, but it's going to get a whole lot worse. And, we are on a time constraint.

They want to move this to .NET and use ClickOnce. And, some brute hackery involving an Internet Explorer embedded container with security switched off. Probably even SXS to host the controls in the Internet Explorer container. They tell me it will be fine, we can just give the home users CDs, and put them through the .NET install (target is 2.0).

Am I worrying over nothing here? Can I really trust ClickOnce/.NET for deployment, even in the future? Is it reasonable to put the home users through the .NET install process?

Upvotes: 0

Views: 310

Answers (3)

user133018
user133018

Reputation: 79

Yeah, honestly using .NET 2.0 the amount of users who do not have it installed is honestly very tiny on Windows based PCs. Almost anyone who uses Windows XP or later has at least .NET 2.0 due to Windows Update.

Pretty much any Windows Vista or Windows 7 user will have it, and I am not sure, but it might have been included with Windows XP Service Pack 2 or 3.

Upvotes: 0

JP Alioto
JP Alioto

Reputation: 45127

Am I worrying over nothing here?

No, I think your concerns are well founded.

Can I really trust ClickOnce/.NET for deployment, even in the future?

Yes, I think so. There's no doubt the world is going toward Rich Internet Applications rather than smart clients, but I don't see any indication that ClickOnce is going away. WPF is delivered over ClickOnce and that's MS flagship presentation framework going forward. It will be around for quite some time.

Is it reasonable to put the home users through the .NET install process?

In my opinion yes. It's very simple, it can be done through Windows Update and as part of the installation of your application (you don't have to ship a CD) and you will find that many of the customers already have it installed.

Upvotes: 1

John Saunders
John Saunders

Reputation: 161811

This sounds like a recipe for disaster, unless it's been done before, and you're using a framework:

an IE embedded container with security switched off. Probably even SXS to host the controls in the IE container.

This sounds like a real mess, and a bad way to combine managed and unmanaged code.

Also, why in the world would you not use .NET 3.5 SP1? If this is an application just now being moved to .NET, then why start in the past?

Upvotes: 3

Related Questions