ClickOnce and Spring.Net

[hakangranstedt]

I'm developing a new ClickOnce application in C# which will be distributed to a lot of client computers. The client computers may have different devices connected. My initial idea was to develop a core application which interacts with device specific modules through an agreed interface. Spring.Net was the natural choice to achieve this dependency injection.

The problem I face is when installing the application - which modules should be added to the installation? I don't want to add references from my core application to the different modules in order to have these included when publishing my core application.

Please help me out of this.

[Erich Eichinger]

I'm sorry - I don't have any experience with ClickOnce. Maybe some other User out there can help?

I'd start by packing the "bootstrap" assemblies - means at least your application core, any interfaces + required spring assemblies for wiring.

In an article about ClickOnce I read about some "declarative list of required files". To me this sounds like there's some way to define additional assemblies and where to find them.

If you find a solution and/or think, spring could help using ClickOne by providing some support please let us know here!

cheers,
Erich

[.ben]

At the company we're starting to uise the ClickOnce approach for all upcoming projects(easy distribution, rich client with webservices). We are currently in the last stages of deploying and beta testing our first click once project. We've used spring on the server and client side. (AOP (client & server), Webservice exporter/consumer (client & server), DI).

While we do deploy every assembly needed on the client, I have read a lot about the ability to download files when needed while using ClickOnce distribution.

Check out: http://msdn2.microsoft.com/en-us/library/ak58kz04(VS.80).aspx .