All,
I created a C# console app in VS2010 (.NET4). that hits a database and sends out emails.
It works fine when I run it from VS but deploying the app to a remote server has me befuddled. All I need to do is install this app on (1) remote windows server.
Should be easy, right?
Looking at the publish settings, I don't see anything that will just build it locally without creating an installer (From a CD-Rom or DVD-ROM) and the other 2 options really don't apply either, at least by their descriptions.
So here is what I did so far:
The VS2010 publishing options that I am given are as follows:
Step #1 Picked option 3
Step #2 Place generated files on remote server
Step #3 Ran the setup installer
Step #4 Get this error
Question
Am I approaching this correctly?
If not, what do I need to do?
Thanks
Notice the error:
The application requires that assembly office Version 12.0.0.0 be installed in the Global Assembly Cache (GAC) first.
Refer to this answer and this MSDN question which contains the answer I have quoted below:
We solved it by going into the Applications Files dialog under the publish tab of the Project's properties and changing the office.dll assembly to Include. It had previously been set to prerequisite (auto). --Dave3182
It looks like your application is leveraging Microsoft Office (2003, I think) COM objects. This will require the same version of Office to be installed on your server.
If you are leveraging Office format files (.doc, .docx, .xls, .xlsx for example), you can look into 3rd party libraries that allow you to create the formatted files without Office installed. If you are just using Outlook to send the emails, you should re-implement the feature using the .NET libraries instead.
Related
I have an App Service in my Azure account which I deployed with Visual Studio Publish wizard. Is it possible to restore the deployed solution locally (in Visual Studio) from the Azure App Service?
When you publish an app to an App Service (web app), just your code is published, not the Visual Studio project / solution files. So no, unless you somehow forcibly packaged (or maybe ftp'd) a copy of your solution files, they won't be available for download.
It's fairly trivial to pull the app down to a local machine though, since Web App has built-in ftp. Just don't count on being able to retrieve source code for languages such as c# and Java (since usually just the dll/jar files are published).
I want to mention one thing which might be helpful if your application is .NET. There are many .NET Decompilation tools today(Reflector, ILSPY, JustDecompile etc.) that can open a .NET DLL and let you view the code (the best one being Telerik's JustDecompile which can create a PROJECT out of a .DLL file or any .NET Assembly)
The code will not look EXACTLY like the one you created but can get you pretty close. Definitely worth a try if you lost your code and looking for some way to get it. This will only work if the code was not obfuscated in the first place. There might some rework required but you can get somewhat close.
I wrote an application with .Net4 and C# and also deploy it to user system with install shield.
After I changed few lines of code, one of my Winforms automatically disposes** without error in client system which has .Net4 but does not have Visual Studio installed.
All prerequisites are installed and it used to work fine...
If I install Visual Studio in client's system, it will work perfectly.
I tried to debug it but visual studio does not find any exception.
Please help
Form may contain components that are not present in client's system.
It depends upon way in which you are deploying your application.
General way is:
Install framework.
Copy-Paste debug folder to client's system.
Bring shortcut to desktop.
OR
Simply publish the application.
Copy paste publish folder to cliet's System.
Execute publishing setup.
Bring shortcut to desktop.
It works in this way.
Hope its helpful
You wrote on the user machine .Net 4 Client framework is installed. Try to uninstall it and install full .Net 4 framework (here is a link to MS download site).
Those 2 lines that you have added may now reference the features that are available only in full .Net 4 installation. (Unfortunately you did not post those lines so we can only guess what the problem is).
With Visual Studio full .Net 4 is installed and maybe because of this your app starts to work after VS installation.
See Difference between .NET 4 Client Profile and Full Framework download for more details.
I've built a Winforms Application, and I want to publish it. I'd like to have a link on a website https://sites.google.com/site/satsavvyboardgame/home where I can have the user download the application and have it install on their computer. So far, I haven't found any way to wrap everything up in one package, or successfully publish to the web. What are the specifications for the URL to publish to the web?
Is there any way to package everything into one item (the site won't allow me to upload/download folders), so that the user could download one item, then run that or something in it?
Is there another way to do this that I haven't seen?
I'm using C# Visual Studio 2010 Express, and my application has the code and a couple of XML files that I need to run. All are part of the project, and run fine when I install from a file using the CD publish settings.
I've never published an application before, so any help would be much appreciated. Thanks!
You have 2 general options:
use "ClickOnce" which will enable automatic updates each time the user click to install and have several other benefits such as less problems with priviliges.
Use "Windows-Installer", which allows you more control of how to do and what to do during the installtion phase. However, shamefully, Package & Deployment project types do not exist anymore in vs2012. there are several 3rd party packages you can work with to create your setup-project.
The ClickOnce is preferable if what the user download is a just a simple standalone game application for example.. the MSI is for the more "rich" applications that should make extensive usage in the machine registry and etc..
The table in this link will give you the data you need to make a decision:
http://msdn.microsoft.com/en-us/library/142dbbz4(v=vs.80).aspx
I'm trying to deploy a WinForm app through clickonce using a ftp site on my dreamhost account. However, when I try to publish, I get the following error:
Failed to connect to 'ftp://ftp.mydomain.com/client' with the following error: Unable to create the Web site 'ftp://ftp.mydomain.com/client'. The components for communicating with FrontPage Server Extensions are not installed.
Here is my settings on the publish tab
Publishing Folder Location: ftp://ftp.mydomain.com/client
Installation Folder URL: http://ftp.mydomain.com/client
It seems that Visual Studio is not realizing I am publishing to a ftp site and not a site with FrontPage.
Does anyone know how to fix this problem?
Visual Studio only supports publishing to web servers that have Frontpage Extensions installed, regardless of whether connecting via FTP or HTTP. If your host doesn't support them, you will have to publish to a local folder and then upload its contents using an FTP client.
UPDATE: The FrontPage extension components need to be installed on the machine you are DEVELOPING on (Used to publish). The server shouldn't matter--it's simply FTP. On your development system, go to control panel > add/remove programs > and repair "Microsoft Visual Studio Web Authoring Component". Depending on the version you have, you may need to repair VS2010, etc. This will reinstall the FP components on YOUR machine, allowing you to publish via FTP.
Do you recently installed Xamarin extensions xamarin.visualstudioInstall.msi ?
This is cause of stopped deployment component.
Check this discusion:
http://forums.xamarin.com/discussion/30406/bug-after-installing-xamarin
Removing 'Xamarin' from the uninstall/change a program fixed the issue for me.
After that VS 2013 and VS 2015 RC1 deployments started to work again.
what is worth of acknowledgment is the fact that Visual Studio 2010 may report such error due to problems with lacking RAM or after several sleep or hibernation phases with VS turned on. I experienced this with a perfectly well configured server which I have used for ages and done hundreds of publishes, the error came all of a sudden and the only medicine was a VS restart (or sometimes the whole machine's restart). Best regards.
According to MSDN specs, you'll have to add some custom content/mime types to your server for ClickOnce:
If you are deploying a ClickOnce application from a Web server
other than IIS, you may experience a problem if the server is
returning the incorrect content type for key ClickOnce files, such as
the deployment manifest and application manifest. To resolve this
problem, see your Web server's Help documentation about how to add new
content types to the server, and make sure that all the file name
extension mappings listed in the following table are in place.
File name extension Content type
=================== ===========================
.application application/x-ms-application
.manifest application/x-ms-manifest
.deploy application/octet-stream
.msu application/octet-stream
.msp application/octet-stream
DreamHost allows you to add custom mime types in a .htaccess file.
How to make generic installation for my C# program, that will work on Win XP, Win 7 32bit and Win 7 64bit ?
I need that all the related components (like Framework... Crystal Reports...MDAC....) will be include and will install only the program that the OS is missing
Thanks in advance
What version of Visual Studio are you using? It matters, because if you're using Express, you're going to need a 3rd party tool If you're using Professional or higher, you can just create a Setup project as described here:
http://support.microsoft.com/kb/307353
if you weren't worried about required components, of course, you could just do an XCOPY deployment, but since you specifically need your prerequisites included with the install, you need to use a tool like the setup project 9which creates an MSI file) or using a third party tool like Installshield.
i think
1- Create 3 separate packages for (Win Xp,Win7-32 , Win7-64)
2- Ask user if user is downloading from the website and push require download from the server. Alternatively , you can write a samll silverlight based application to get the details of user machine.
3- If 2 point is not true than while installing on a user machine get the details first and choose manually which pakage to install.
why i am telling to create specific package because of Microsoft issues pathches time to time and you may need to change the package so keep it seperate will definately help you.