Archive for the ‘Deployment’ Category
Error: The installer was interrupted [AppName] could not be installed
Posted by: admin in .NET, ASP.Net, ASPX Error, Deployment on November 2nd, 2011
Installing a .net application on different platforms would be a headache if you are not familiar with every details on how it work.
One of the error more often happened is the “The Installer was interrupted [AppName] could be installed. You need to restart the installer to try again.” as depicted below
To resolve this issue, there’s a service that need to be enabled “IIS Metabase and IIS 6 configuration compatibility”
Under windows 7:
- Go to Control Panel
- Programs
- Turns windows features on or off.
- Launch the Server Manager
- Roles
- enable the IIS Metabase and IIS 6 configuration compatibility
An error occurred while validating. HRESULT = ’80004005′
Posted by: admin in .NET, Deployment, Exception on July 27th, 2010
An error occurred while validating. HRESULT = ’80004005′, this error just came up when I’m trying to organize my .Net Project files in my Solution, I removed some of the projects and just use the compiled dll in referencing to the main Project. However, this error has appeared during rebuilding the setup project and it took some of my time to find the solution or the cause.
So, what I did was I removed all References from the Target Primary Output project and added them and rebuilding it again , 
that’s it no more errors.
“Thank you for reporting this issue. We were able to reproduce the problem and have identified the root cause. The problem is caused by cross-solution project reference between Solution1 and Solution2. From the attached project, the project “WindowsFormApplication1” in Solution2 references a project that is not in Solution2 (it references ClassLibrary1 from Solution1). To fix the error, the workaround is to copy the ClassLibrary1 project to Solution2 and re-add the reference to ClassLibrary1 within its own solution.
Project-to-project references only works within the same solution. If you have to split into two solutions and split the code for your class library into two projects, you need to also split the project that references the class library into two projects (one for each solution) in order to avoid project references outside the current solution.
I hope this helps.
Candy Chiang
Program Manager – Visual Studio”
For more information and explanation about this error just click here
Error 1001. Exception occurred while initializing the installation. System.IO.FileNotFoundException
Posted by: admin in .NET, Deployment, Exception on June 22nd, 2010
This error occurs when the CustomActionData has a supplied value,
Example:
The value of the CustomActionData is /TARGETDIR=[TARGETDIR], what you need to do is to update it to /TARGETDIR=”[TARGETDIR]\”
How to get msi setup file location using installer class
Posted by: admin in .NET, Deployment on June 21st, 2010
To get the current msi setup path,
- Goto the setup project
- Right click and select view->custom actions
- Under Install Node, click the “primary output from….”
- Press F4 to show its property
- Add the /Source=[SourceDir] to the CustomActionData property
- Can then be access through the installer class
Context.Parameters(“Source”)
Source Path Custom Action
The install location for prerequisites has not been set to
Posted by: admin in .NET, Deployment on June 9th, 2010
Follow this steps to solve this problem:
Update the Package Data
- Open the [Program Files]\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder or %ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems
- Edit the Product.xml file in Notepad.
- Paste the following into the < PackageFiles > element:
- Find the element for < PackageFile Name=”dotNetFX30\XPSEPSC-x86-en-US.exe” and change the PublicKey value to:
3082010A0282010100A2DB0A8DCFC2C1499BCDAA3A34AD23596BDB6CBE2122B79
4C8EAAEBFC6D526C232118BBCDA5D2CFB36561E152BAE8F0DDD14A36E284C7F163
F41AC8D40B146880DD98194AD9706D05744765CEAF1FC0EE27F74A333CB74E5EFE
361A17E03B745FFD53E12D5B0CA5E0DD07BF2B7130DFC606A2885758CB7ADBC85E
817B490BEF516B6625DED11DF3AEE215B8BAF8073C345E3958977609BE7AD77C13
78D33142F13DB62C9AE1AA94F9867ADD420393071E08D6746E2C61CF40D5074412
FE805246A216B49B092C4B239C742A56D5C184AAB8FD78E833E780A47D8A4B2842
3C3E2F27B66B14A74BD26414B9C6114604E30C882F3D00B707CEE554D77D208557
6810203010001 - Find the element for < PackageFile Name=”dotNetFX30\XPSEPSC-amd64-en-US.exe” and change the PublicKey value to the same as in step 4 above
- Save the product.xml file
Download and Extract the Core Installation Files
- Navigate to the following URL: http://go.microsoft.com/fwlink?LinkID=118080
- Download the dotNetFx35.exe file to your local disk.
- Open a Command Prompt window and change to the directory to which you downloaded dotNetFx35.exe.
- At the command prompt, type:
dotNetFx35.exe /x:.
This will extract the Framework files to a folder named “WCU” in the current directory.
Copy the contents of the WCU\dotNetFramework folder and paste them in the %Program Files%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 folder (%ProgramFiles(x86)%\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFx35SP1 on x64 operating systems).
Note: Do not copy the WCU\dotNetFramework folder itself. There should be 5 folders under the WCU folder, and each of these should now appear in the DotNetFx35SP1 folder. The folder structure should resemble the following: DotNetFx35SP1 (folder)
-
- dotNetFX20 (folder
- dotNetFX30 (folder)
- dotNetFX35 (folder)
- dotNetMSP (folder)
- TOOLS folder)
- en (or some other localized folder)
- dotNetFx35setup.exe (file)
You may now delete the files and folders you downloaded and extracted in steps 2 and 4.
You can read more on the attached readme file.
How to change application setting during installation in .net
Posted by: admin in .NET, Deployment on July 8th, 2009
Follow this thread for the details of required steps to accomplish this problem.
How to Create Installer for Windows Service Project
Posted by: admin in .NET, Deployment on May 6th, 2009
To create a setup project for your service
- In Solution Explorer, right-click to select your solution, point to Add, and then click New Project.
- In the Project Types pane, select the Setup and Deployment Projects folder.
- In the Templates pane, select Setup Project. Name the project MyServiceSetup. Click OK.
A setup project is added to the solution.
Next you will add the output from the Windows service project, MyNewService.exe, to the setup.
To add MyNewService.exe to the setup project
- In Solution Explorer, right-click MyServiceSetup, point to Add, then choose Project Output.
The Add Project Output Group dialog box appears.
- MyNewService is selected in the Project box.
- From the list box, select Primary Output, and click OK.
A project item for the primary output of MyNewService is added to the setup project.
Now add a custom action to install the MyNewService.exe file.
To add a custom action to the setup project
- In Solution Explorer, right-click the setup project, point to View, and then click Custom Actions.
The Custom Actions editor appears.
- In the Custom Actions editor, right-click the Custom Actions node and choose Add Custom Action.
The Select Item in Project dialog box appears.
- Double-click the Application Folder in the list box to open it, select Primary Output from MyNewService (Active), and click OK.
The primary output is added to all four nodes of the custom actions — Install, Commit, Rollback, and Uninstall.
- In Solution Explorer, right-click the MyServiceSetup project and click Build.
How to Create Uninstall
Posted by: admin in Deployment on April 1st, 2009
Introduction
It’s super easy to add this to your deployment project.
- Select your deployment project and go to the file system editor, user programs menu.
- Add an additional shortcut to your primary output project and name it Uninstall Application.
- Set the Arguments property to /u=[ProductCode].
- Add the following code to your project’s Main() sub or startup form’s New() sub just before the call to InitializeComponent().
Dim arguments As String() = Environment.GetCommandLineArgs()
Dim argument As String
For Each argument In arguments
If argument.Split(“=”)(0).ToLower = “/u” Then
Dim guid As String = argument.Split(“=”)(1)
Dim path As String = _
Environment.GetFolderPath(Environment.SpecialFolder.System)
Dim si As New ProcessStartInfo(path & _
“\msiexec.exe”, “/i ” & guid)
Process.Start(si)
Close()
Application.Exit()
End
End If
Next
That’s is! The Deployment project will replace [ProductCode] in the Arguments property with the actual installer project’s ProductCode GUID value. Your program will see the /u={Actual ProductCode} argument and pass it to msiexec.exe before exiting.
The installer is run in repair/remove mode for your application. The user is allowed to select repair or remove, and continue. If you want the product to remove only, replace the “/i ” with “/x “.
Source: http://www.codeproject.com/KB/install/DeployUninstall.aspx
How to Debug Installer Class
Posted by: admin in Deployment on March 31st, 2009
To Debug Install Class;
Public Overrides Sub Install(ByVal stateSaver As System.Collections.IDictionary)
#If DEBUG Then
System.Diagnostics.Debugger.Break()
#End If
MyBase.Install(stateSaver)
End Sub