My solution(.net frame work 4.6) composed of one main project with 3 reference projects(class library). If I run setup file created by Installshied which finally install main.exe with 3 dlls and sytem.value.tuple. However, setup file created by visual studio setup project, it install lots of dlls in application folder. I set .net 4.6 launch condition both software.
Visual studio looks installed all the .net assemblies I used. What's wrong with visual studio or what I missing?
Update:
I gave up.... But adding main.exe file instead of primary output of project. That's my current solution
Related
I just created CordovaApp (Multi-Device Hybrid App) in VS 2013. The application was working fine. Then I tried to open app with VS 2015 Community edition in another machine (and on same machine) and I am receiving following error:
Severity Code Description Project File Line Suppression State
Error The specified directory to the Visual Studio extension
D:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO
14.0\COMMON7\IDE\EXTENSIONS\APACHECORDOVATOOLS\node.exe either does not exist, or does not contain a packages\vs-mda sub-directory. Please
check that the extension directory exists and set the MDAVsixDir
variable to the correct
directory. MyAppCordovaApp C:\Users\foouser\AppData\Roaming\npm\node_modules\vs-mda-targets\Microsoft.MDA.targets 105
I also installed Cordova Tools for VS update 6.
Is there any known work-around for this issue?
I am facing the same issue. Cordova project created in VS2013 is not going to run/debug at VS2015.
NodeJS module used for building the project is no longer called vs-mda (i.e. Visual Studio Multi-Device Application) but vs-tac (i.e. Visual Studio Tools for Apache Cordova).
After perform manual migration, it is working now.
See reference:-
http://mariusbancila.ro/blog/2015/07/31/migrating-a-cordova-project-from-visual-studio-2013-to-visual-studio-2015/
I've updated to Visual Studio 2013 Update 4, which includes Typescript 1.4. I've updated my project file with this, and everything works fine locally.
<TypeScriptToolsVersion>1.4</TypeScriptToolsVersion>
However, the build server has not been updated with the Typescript 1.4 SDK. Builds are now failing with this error message:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\TypeScript\Microsoft.TypeScript.targets (95): Your project file uses a different version of the TypeScript compiler and tools than is currently installed on this machine. No compiler was found at C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.4\tsc.exe. You may be able to fix this problem by changing the element in your project file.
Despite the existence of the VisualStudio folder referenced above, Visual Studio is not installed on this machine, and I'd prefer not to install it. It seems I need to install the Typescript 1.4 SDK, but I can't find a stand-alone installer for it anywhere. http://www.typescriptlang.org/#Download has npm and VS add-in downloads, but no stand-alone SDK.
This seems a little silly, but where can I get a typescript 1.4 SDK from?
The Visual Studio add-in is also the stand alone Typescript 1.4 installer.
You can get the installer here.
Does anyone know the components that need to be installed in order to make the Package Target available via MSBuild.
It's possible to Package using MSBuild on a machine with Visual Studio installed, but not on a build server with only the .NET 4 SDK and Web Deploy 2.0 installed, which results in the following error:
msbuild "Package" does not exist in the project.
It partly comes down to the following missing files on the server:
c:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\*.*
This can of course be resolved by copying the contents of the MSBuild VisualStudio folder to the equivalent directory on the build server, but this is not a manageable solution for server configuration.
All the answers I've read involve having Visual Studio installed or copying the files. Surely it's possible to compile the Web Deploy package without installing Visual Studio?
I have a TeamCity CI server without VS installed building a Web Project configured to also create a deployment package on successful build. However, for the life of me I can't recall if I copied those files manually or if they were installed by some component.
The relevant components I have installed are the following, if you want to give it a shot:
.NET 4.0 SDK;
Microsoft Visual Studio 2010 Shell (Integrated) Redistributable Package;
Visual Studio 2010 SDK; (Not the VS 2010 SDK SP1)
Microsoft Visual Studio 2010 Visualization & Modeling SDK;
Web Deploy 2.0;
I installed the VS Shell in order to be able to install the VS 2010 SDK which in turn was required in order to install the Visualization & Modeling SDK so that I was able to run T4 transformations on the build server.
With this components and configuring the following MSBuild properties DeployOnBuild=true;DeployTarget=Package to create the deploy package I had no problems, but as I said earlier I may have copied the files manually after giving up all hope of finding a more cleaner solution and now my brain is blocking any memory of such ill action.
I have a C++/CLI app that is built under Visual Studio 2010 but using .Net 3.5. As required, I hand edited my project file to add the TargetFrameworkVersion with a value of 3.5 and was able to build it without issue when I was in x86 (32-bit) mode. However, when I switched to build it in x64 (64-bit) mode, I got the following error:
error MSB8014: Execution path (C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\x86_amd64) could not be found.
I do have VS 2008 (9.0) installed, but there is no x86_amd64 directory under the bin folder. I tried fooling it by adding this folder (and the amd64 folder which would have failed thanks to the next line in the targets file), and then I got the error:
fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
which I can't figure out because my project has no explicit links. I switched the C# assemblies that it interacts with to build in x64 (as opposed to any CPU) but to no avail.
FYI: Everything builds correctly in 32-bit mode. Everything also build correctly in 64 bit mode if I switch to .Net 4.0 (v100). I get the same errors building in both release and debug mode.
Any ideas would be appreciated.
If you are compiling with the "toolset" changed over from V100 to V90 on the project properties, and you have Visual Studio 2008 installed on the same development machine, just go to Control Panel, Programs and Features, select Visual Studio 2008, right-click, select Uninstall/Change, then select to add/remove f eatures, then when you are presented with a list of features, look for x64 compiler/files under Visual C++ which is not installed by default,but by clicking on the checkbox next to it, it will add the needed files.
In VS2010 it should link to C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64
You probably got configuration wrong, or imported from a vs2008 project.
Go to Configuration -> General -> Platform Toolset. make sure it's v100 (vs2010)
If that doesn't help , look at Configuration -> VC++ Directories. That's where that path is set.
You can see that it looks in $(VCInstallDir) which in your computer is set to the VS2008 path.
I have a big solution file and few projects can not be loaded. I do have all the files in the proper directories. But when I right click and try to load the project, I get the following error:
The project file "C:\myapp.proj" can not be opened. The project type is not supported by this installation.
By the way, these projects are related to Windows Workflow.
Please help.
I am using Visual Studio 2005 on Win7 machine.
It might be a modeling project, test project, silverlight/wpf project etc. It's definetely something that's not supported by your version of Visual Studio, you should use a newer version or a different one (i.e. professional instead of express).
Update: I did not see that it was Windows Workflow Foundation. Check out this link, it's a toolkit for using Workflows in VS2005.