I am creating a stand alone application for a client and I am going to use Microsoft Enterprise Library. My question is do I need to install Microsoft Enterprise Library on client machine too for the application to work?
Thanks in advance for your replies.
No you shouldn't need to install it on the client machine, as long as you include the dependent DLLs with your installer.
If the references have "Copy Local" set to true, when you build your application, it will copy the DLLs to your output directory, and so it will not need them installed in the GAC.
You don't have to "install" it separately per se, you just have to copy the DLL to where your application's assembly is installed at. Depending on your settings, visual studio already does this for you.
Related
i created a windows form application in VS2010 using QBSDK.
my problem is that the target has QB installed and running, but i get an error when trying to deploy my one-click application. (the error is just that the application generated an error - and i cannot find the log file to see what actually happened).
to solve it, If i install the QBSDK onto the target machine, it runs fine.
My question is:
what do i need to include in my deployment so i DONT have to install the SDK?
You need to install the SDK redistributable components for any application that uses the SDK to work. If you are using QBFC, RDS or the QBO connector, there are only two supported ways to distribute these components:
1. You can use the stand-alone compressed-image installers that Intuit provides.
2. You can use the merge modules that Intuit provides.
I don't use ClickOnce deployment, but I think that if you are using ClickOnce deployment you can not include merge modules. I think there's a way to create a custom prerequisite that will install using the stand alone installer; http://msdn.microsoft.com/en-us/library/ms165429%28VS.80%29.aspx
If you don't want to go that route, you would need to use another deployment option. In Visual Studio 2010, you can create a Visual Studio Installer Setup Project that you can add the merge modules into. This project type is NOT available in the Express editions of Visual Studio, though.
There is a section in the QBSDK Programmer's Guide that gives some more details about deploying the SDK with your application.
Created a windows service in VS2012. Right clicked on the service and selected 'Add Installer' as done in VS2010
Got the message:
Unable to add installer. The designer could not add a Project Installer.
Anybody run into this ?
Check to see if the files already exist. In my case, a previous developer excluded the installer files from the project, so I did not see them until I opened a Windows Explorer on the source folder.
Do you have an Express version? I have not run into this problem with Visual Studio Professional 2012 on Windows 8 N Pro. I can right click on the designer surface and click on item "Add Installer" and a class is created called 'ProjectInstaller'.
You can create the project installer class manually. Designers are overrated anyway. I have written a blog article on how to do this.
Simple Installer for Windows Service Using Visual Studio 2012
Is there a reason you need a deployment wizard? Is there a configuration parameter you need to prompt the installing user with? I generally just use a configuration file and package up each environment's configuration with the deployable.
The Project Installer is not included in VS 2012. If you right click your solution and choose Add, New Project, then go to Other Project Types and choose Setup and Deployment, it should take you to the InstallShield page where you can download and install the Limited edition of InstallShield for free (you will have to register and get an activation code via email). Once installed, repeat the steps above and it should prompt you to either register the software or continue with a trial version.
How do I install the Entity Framework on my build server? I only have MS Visual Studio Shell installed there and there is no Package Manager Console.
Thanks.
Do one of the following
Add the EF assemblies to source control so they can be downloaded on checkout
Enable nuget package restore and allow the build server access to the internet to download the packages.
You don't need to install EntityFramework on your build server. EntityFramework is part of the BCL, so all you have to do is install .NET on your build server. Now if you need to use some extensions that are available through NuGet packages, all you need to do is to add reference to those packages in your project and then all the necessary assemblies will be part of the web application. Thus the web application is self-contained. All you have to do is to put them under source control so that the build server is able to retrieve them.
I am using EF 4.0, at the time I am writing these lines I heard that EF 4.1 update 1 has been released and EF 4.2 is in beta. From wikipedia
A refresh of version 4.1 named Entity Framework 4.1 Update 1, was
released on July 25, 2011. It includes bug fixes and new supported
types.
But I only found a link of Version 4.1.10311.0 from Microsoft which date published is 3/21/2011. So I wonder if version 4.1.10311.0 is the latest release so far. If it's not, where can I download the latest release ?
ps : For some reasons I can't use live update, I need to download package to install manually.
From Arthur Vickers:
What if I can’t use NuGet? What if you can’t connect to the Internet
from your development machine. Or what if you are not allowed to
install NuGet on your machine. Don’t worry; all is not lost.
First you need to get the NuGet package. For this you do need to be
able to connect to the Internet from some machine—but it doesn’t have
to be your development machine. You’re reading this so presumably
you’re not completely off-the-grid. :-)
You can get the package by using NuGet in Visual Studio on a machine
connected to the Internet in the normal way—just install the package
you want into a dummy project. After installing the package you can
find the .nupkg file either in the dummy project folder or by browsing
the Package Cache from the Package Manager Settings menu option.
You can also get the package without Visual Studio by using NuGet.exe.
If you are able to install NuGet on your development machine then do
so and setup a local feed. This may sound daunting but it’s really
easy. Copy the .nupkg file to your local feed and then use NuGet to
install it in the normal way—with no connection to the Internet
required.
If you can’t install NuGet on your development machine then take the
.nupkg file and rename it to .zip—yep, it’s a zip file. You can now
extract EntityFramework.dll from the zip file and use it as you would
any other assembly. Note that you will not get any of the automatic
project-level integration I mentioned above, so you may have to do
more manual configuration of your project.
If you are using EFv4.0 you mostly don't need EFv4.1 or EFv4.2. Those versions bring new type of mapping (code first / fluent) and new DbContext API which can be used instead of ObjectContext API. So unless you want to start a new project with those "new" features or completely migrate your existing project you don't need it. Real new functionality for you will be included in .NET 4.5. DbContext API and code first is shipped only as NuGet package since EFv4.2.
use the package-manager in VS2010 to install
Tools + Library Package Manager + Nuget package manager
EF 4.2 has just been released: http://blogs.msdn.com/b/adonet/archive/2011/11/01/ef-4-2-released.aspx
This is a minor update over 4.1.
The runtime components are available via NuGet. The designer etc. updates for VS are a separate install.
I need to know whether to work with sharepoint templates I have to have visual studio installed on the server?
No. Developers create solution packages during development and you deploy those solution packages to the server(s) using the Solutions Framework.
See http://msdn.microsoft.com/en-us/library/aa544500.aspx