I have a solution containing several projects, as well as some projects that get copied into subfolders relative to the main application. Is there any possibility to deploy this using ClickOnce? Or should i create a seperate project including references to my built files just for clickonce deployment?
What is the actual problem you are having?
Referenced assemblies are included automatically, and if I add an .EXE to a subfolder of my Project it shows up in the Application Files dialog of Project|Publish.
Related
I'm building an ASP.NET web portal for a project for school.
I use a three tier architecture and I'm trying to publish it using FTP.
The web project is published successfully but the other two projects aren't published on the IIS.
How can I tell visual studio that I want these projects published alongside the web project?
here is an image to make it a bit more clear
http://i.imgur.com/J4qeyTj.png
Thanks in advance
No need to publish other projects separately.
Give reference of other project to your main project.
Publish Main Project.
DLL's of all projects will get created in bin folder[you will get this folder in publish folder].
Just upload files in bin folder to FTP.
You don't need to publish the class library projects.
All you have to do is to add references of your class library projects in your web application and publish it. It'll add your class library projects dll in bin folder of your published folder.
Visual Studio is creating a \bin folder and copying various assemblies into it when I open a web application solution, even before I compile
What is triggering this action?
And how do I control it?
Reason I'm questioning the process, is the assemblies are not the expected ones
This is where Visual Studio puts all the dlls for runtime for your project. Library dependencies that the project needs. All the dlls that Visual Studio needs for a web project are kept here as well as other packages from Nuget that you might add, and your own. If you look in the References section in the Web Project, you will see many of the dlls that appear in the bin directory.
If there are some assemblies there that you do not want. You can try removing the reference from the Reference folder. Right click on the library in the Reference folder and select remove.
Be careful with removing references though, because your project may need it to function.
I am beginner with SVN projects ( Working SVN with ASP.NET MVC3 c# ). I use ankhsvn in
my project.
I load my project in other pc with File -> Open -> Subversion Project
But i found some dlls are missing in the solution explorer.
I explore project folders, there is some folders are without tick icon,
and some reference dlls are packages folder. this folder is with out the tick icon
Please see this images below.
How can i solve this issue. Please Help.
May be the reference path is different after downloading. You can define the correct path
I have a Visual Studio 2010 solution that contains 3 projects: a dll project, an executable project, and the Installer project.
I am working on the dll and the executable concurrently. The executable is simply a front end for the library. While developing the two in Visual Studio I simply added a reference to the dll project from within the executable and it works fine.
What I'm having trouble with is the deployment. Ideally the dll would be compiled and installed in a subdirectory of the executable. Using the "Visual Studio Installer - Setup Wizard" project template for my installer doesn't seem to be giving me the options I need.
Am I going about this wrong by developing my backend and frontend in different projects? What steps should I take to deploy the compiled dll along with the executable? I may be going about this all wrong, so please help me understand a better methodology if this seems backwards. For all the programming I learned in college, no one ever went over what I do when I actually want to deploy my software.
Since the DLL project is explicitly referenced from the EXE project, it is automatically copied in the EXE's build folder (i.e. bin\Debug or bin\Release) and is considered part of EXE project's "primary output". As a consequence, you only need to reference the EXE from your setup project.
The installed DLL will be in the same folder as EXE. Why would you want to install the DLL in a different folder on the user's machine if it is not there on the development machine? If you are loading it dynamically and using reflection, then don't reference it from EXE, but do reference it from the setup project, which then gives you the power to set whatever target folder you want.
This is what you need to do.
On your Solution create new Project > Other project Types > Click Setup and Deployment
On The Application Folder > right click > Then Add your front end Application > Build.
Check this
Regards
I have a DLL I need to deploy with my C# application. It's not currently included in the installation package when I hit "Publish" so how do I include it?
Would the process be any different if I had app.config and other files I wanted to deploy with my application?
If it's referenced it should be included automatically. I've deployed a couple of apps that require a 3rd party dll and they've published OK.
Is the dll referenced correctly in your project? That's the only thing I can think of at the moment that might be the problem, but if it wasn't your code wouldn't compile and/or link anyway.
To get the xls file to deploy all you need to do is add the file to the solution and then set the "Copy to Output Directory" property on the file.
I take it you are using Visual Studio?
If your using Visual Studio 2008 (I have no experience with Visual Studio 2005) under the Publish tab in your project properties click on the Application Files button. This will bring up a list of all dependencies assembalies required by your project. If you find that required dll is not being published by the Visual Studio publisher tool by default you can go into here and set the Publish Status of the offending dll to Include.
Sometimes in my more complicated projects, depending on the type of dependency, I have to go into this menu and force certain dll's to be included opposed to the default Prerequsite setting.
...but this is all under the assumption you have the assembly properly referenced in the required projects and everything is compiling fine.
Can't you add the dll as a resource to your installer project?