Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have a requirement of publishing three different applications( WPF - *exe) using ClickOnce deployment approach. This is very much similar to the MS Office suite where we have multiple office application which gets installed in one go. Do anyone know the ways to achieve this using VS 2012
If you want to use ClickOnce, you have to publish the applications separately, and the user has to install the applications separately (but you can group them together on the user's Start menu). Otherwise you want to look into WiX or InstallShield or some other product.
To get them to group together on the Start menu, set the Publisher name and Suite name to the same values, and set the Product Name to the name of the application.
For example, if you set the Publisher Name to Contoso and the Suite name to FunWithClickOnce, you will see an entry on the start menu for Contoso, and under it you will see the suite "FunWithClickOnce", and under that you will see the application.
Note that if you leave the suite name blank, it will just put the applications under the start folder for the publisher name.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 1 year ago.
Improve this question
I have a WPF application published via ClickOnce. When deleting it, I also need to delete some files that are no longer needed by the user.
ClickOnce doesn't seem to support adding custom install or uninstall actions.
Please advise some installer that would support custom uninstallation actions.
I would suggest Inno Setup, that supports a lot of scripting and is open source. (https://jrsoftware.org/isinfo.php)
It will allow you to perform an action like:
[UninstallDelete]
Type: filesandordirs; Name: "{localappdata}\<my game folder>"
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I will create four projects each other works together.
desktop program ( as User Interface for entering datas )
web site ( for reporting )
web service ( for connecting database - from desktop program and reporting portal )
windows service ( for sending datas which are entered by users via desktop program to database )
Should i create one Visual Studio Solution which contains these four projects, or should i create different solutions for each of them?
What are the advantages of creating just one solution ?
Thank you.
For what it's worth, here are some significant pros and cons which may affect you:
If you put them all in the same solution, it will be very easy to share code between them-- e.g. projects in a solution can reference another project assembly in the solution as a reference directly, making debugging very nice. Nuget packages will share a common folder if they are shared, and you can see everything nicely at the same time.
However, if you these are programs that run independently but interact with each other, debugging is sometimes easier if they are in separate solutions, so separate copies of visual studio can be debugging the separate pieces simultaneously.
With one solution you will need to start only one VisualStudio instance, where you access code from different projects at once.
All possible refactorings(renaming, signature changing etc) can be easily done when you using one solution. With different solution you will never know if you remove/rename some code used by project from another solution.
You will be able to build all projects at once. Execute all possible unit and integration tests (if you have such)
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
Mine is a .NET and Sitecore based application. How do I check for my application if it's using ImageMagick or any related plugin or not?
Normally, a .NET library (such as Magick.NET) would be used. Look through every project's references to see if any of them says "Magick" or "ImageMagick".
In some projects, ImageMagick may be invoked directly, since it's a command-line tool. To find if that's the case, just use full-text search in your solution. Go to menu Edit –> Find and Replace –> Find in Files, select "Entire Solution" in the "Look in" drop-down list, and search for "magick".
To see whether there are any ImageMagick binaries in the solution, open your solution's folder in Windows Explorer, press Ctrl+F and search for "magick" and "imagemagick".
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have created a Windows Forms application in .NET 4.0. Now there are about 20 client machines where the application has to be reinstalled every time there is a build change.
Is there a way I can push the application to all the machines in the client network in a single go?
ClickOnce is your friend.
In short, ClickOnce allows you to publish an application to a server and users can browse to an associated installation website and install your software.
If your ClickOnce settings are set properly, each time the user launches the application, the application will check for an update on the server, download it if it exists and update then application.
It's worth noting that with each update, the entire application is re-installed. This can save you a ton of headaches but if your application is large, it could be a nightmare for your users if you update the system frequently. Hit the link provided above for all of Microsoft's information regarding this deployment mechanism.
You can have your sysadmin create a Group Policy to do this.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am about to setup my first windows application which is built in C# Visual studio 2010 to my customer.
I want to limit usage to only one computer per installation, but I don't know how to do that.
Can anyone guide me on how I might accomplish this?
Typically this is managed by what's called a "product activation" system. When the customer installs your application, they must enter a serial number or key to "activate" it. If they don't do this, the application remains locked. When they activate your product, the system calls back into your server and says "Hey, this key has been used, and this is the machine it was used on. don't let anyone else use this key again."
http://en.wikipedia.org/wiki/Product_activation
You probably don't want to write this yourself, so there are many third party packages you can purchase to make it difficult for your client to install on multiple machines. There's a fine line though between alienating your client by treating them like a criminal, and trying to protect your hard work.
Pirates gonna pirate.
Encrypt the serial number of the hard-drive into your program. It must be saved to a DB of some kind. Name the field something obscure (not related to a HDD serial #). Then check that it matches every time the app is launched. Not super-high tech, not super-secure, but will work in most situatons. If someone copies the app to another PC, display a message not related to copying the app, but you will know what happened. I've been doing it for years in VB and .NET. Works fine.