Installshield Edition :We are using Installshield 2012 premier edition.
Issue Facing: Unable to register the DLL files to GAC (Global Assembly Cache) using Installshield 2012.
Installshield Implementaion :
Step 1 : created one component under a feature and kept the destination as [Global assembly Cache] folder.
Step 2 : In same component under "Advance Setting" have created a "New .Net Assembly" and provide the details along with the "Publictokenkey".
All our assemblies are Strongly Named.
Our aim is to place our assemblies into "C:\Windows\Microsoft.NET\assembly\GAC_MSIL" location for the registration of our binaries into GAC.
Kindly provide your suggestions regarding this.
Related
I am using BizTalk 2020 and I have a project that I recently upgraded from BizTalk 2006. I have into the following error:
BTSTask.exe AddResource -Type:BizTalkAssembly -Source:"....\xxx.dll" -ApplicationName:"app1" -Options:GacOnAdd,GacOnImport,GacOnInstall
Microsoft (R) BizTalk Application Deployment Utility Version 3.13.717.0
Copyright (c) Microsoft Corporation. All rights reserved.
EXEC : error : File "....\xxx.dll" is not a valid BizTalk assembly. [F:\GIT\xxx\xxx.Deployment\Deployment.btdfproj]
Could not load file or assembly 'xxx.dll' or one of its dependencies. The system cannot find the path specified.
Command failed with 1 errors, 0 warnings.
What I have tried:
I check all the referenced assemblies and they are correct and in the GAC.
I have given access to the temp folder, for the account Network service.
in the deployment section of the project I have provided the target application name.
I have seen that the orchestration that is failing is of type System.Biztalk.BiztalkAssembly where the project that are of type System.Biztalk.Assembly deployed successfully. Could as yet not determine why there is a difference in the projects.
I am using Deployment framework 5.8 if that is of help.
Due to the error message...
"Could not load file or assembly 'xxx.dll' or one of its dependencies.
The system cannot find the path specified."
...you likely have an unwanted, incorrect version, incorrect .NET Framework version, or missing DLL referenced by your DLL.
I suggest downloading a free decompiler such as Telerik JustDecompile or JetBrains dotPeek, opening up your DLL in it, and carefully inspecting the references. The tool might even flag the problematic reference. Carefully check that the referenced DLL's exist on disk, that they are for the correct BizTalk version and matching .NET Framework version. There's a good chance that something was overlooked in the upgrade from BizTalk 2006.
I have problems with my InstallShield projects, that are using InstallerClasses, during the Major Upgrade. The setup is calling the old version InstallerClass or just throws error 1001.
I decided to use the DTF technology, but I am unable to link the generated *.CA.dll file to the "DLL Filekey" property. I am linking the project as a "primary output".
Any idea how can I use the DTF custom action project and link it to Basic MSI Installshield 2012 project? I want to avoid referencing the CA file directly because I am creating automated builds.
Many thanks,
Marek
I'm working with a pre-existing codebase from a software developer that has left my company. I've downloaded the source code from the repository. When I attempt to build the project, I get an error that says:
The type or namespace name 'Diagnostics' does not exist in the namespace 'Microsoft.WindowsAzure' (are you missing an assembly reference?)
I can't figure out how to get this project up-and-running. When I look at the NuGet packages associated with the project, I can see that the Windows Azure Configuration Manager and Windows Azure Storage packages are already installed. I'm not sure what I'm missing though.
Can someone tell me what I need to install on my machine to get past this error? Thanks!
I recently had this error. The problem was that the project was referencing Framework 3.5 and I have the 2.4 SDK installed which targets 4.0. Upgrade your project to target 4.0 and you should be fine.
I was getting this error on Visual Studio 2015 Update 3. This project's Azure Tools verion is 2.9.
I resolved this error by right clicking References under the project that has the error, then clicking Add Reference, then click Extensions under Assemblies. Find Microsoft.WindowsAzure.Diagnostics, check the box, and click OK. Now try rebuilding your project and hope for a different error.
The assembly should exist on your computer here: C:\Program Files\Microsoft SDKs\Azure.NET SDK\v2.9\bin\plugins\Diagnostics\Microsoft.WindowsAzure.Diagnostics.dll
If you do not see this assembly, it's most likely because you do not have the required Azure SDK. If you are using Azure SDK v2.9 like I am, you can download the SDKs here: Microsoft Azure SDK for .NET - 2.9
Then click download and select:
MicrosoftAzureLibsForNet-x64.msi (Microsoft Azure Client Libraries for .NET)
MicrosoftAzureTools.VS.140 (Microsoft Azure Tools for Microsoft Visual Studio 2015)
If you are using Azure SDK v2.7 then you will want to use this link: Microsoft Azure SDK for .NET - 2.7
i am going to make setup file with installshield 2010.(my program is written .net frame work 4). according to installation requirement in install shield, i mark microsoft .net framework 4 full full and client package but after make set up when i want to set the setup file, there is error that "you must have .net framework 4 in your system".
i want to set the .net framework 4.0 during the installation in client computer, but i face with that error:you must have .net framework 4 in your system.
please help me
I realize that this is an old thread, but I came upon it while searching for an answer to the same question.
In my version of InstallShield 2010 Professional, the .Net 4.0 redistributable was not available and, as 2010 is no longer supported, you could not get it from the redistributable downloader in the Tools menu. There is a InstallShield 2010 Expansion Pack patch that can be downloaded and run which will include it.
I installed it and it worked fine for me.
Do you use Prerequisites in InstallShield?
If yes, please check if this prerequisite is downloaded to you local system.
You can see this here:
"Application Data->Prerequisites->Microsoft .NET Framework 4.0 Full" column Location
If it has value "Needs to be downloaded" do the right click and choose Download selected item...
I created a utility library for my Sharepoint WebParts. Now when I reference this library from my WebPart project, it compiles fine, but the library is not included in the .wsp package. This means the library assembly is not deployed to the target system, causign the WebPart to fail.
Is there any way to fix this? I am using Visual Studio 08 & VseWSS 1.2.
Brij's answer is partially correct, your VSeWSS version is the problem. This feature only came in version 1.3 (I recommend the March CTP) to have the CopyToLocal=true automatically add the assemblies to the GAC for you.
Right click of Assembly > Properties
Set “Copy Local” property = true
Build project.
See following for more details:
http://urenjoy.blogspot.com/2009/08/add-assembly-wsp-vsewss.html