i want to run the conf.ts in visual studio 2013 with type script. i have added the conf.ts, spec.ts and required typing. it looks as below.
There are 0 build errors. if i run the conf.ts, it is going to local host which is mentioned in the project properties and not to the base path have mentioned in the spec.ts. how to resolve this issue?
project in VS 2013
Related
I created a new .NET 6 worker service project with dotnet new worker -n MyProject. I then created a new solution with dotnet sln new -n MySolution. Finally I added the project to the solution with dotnet sln add .\MyProject\MyProject.csproj. When I opened the solution in Visual Studio 2022, I was greeted with a bunch of "errors" in the default Worker.cs file:
The project will build and run just fine. The problem appears to be with the new Implicit Usings feature of .NET 6. Visual Studio is not recognizing that the red-underlined items are implicitly imported from their namespaces, and don't have to be referenced manually. There is an additional error in the error list:
Project "C:\LongDirectoryPathHere\MyProject\obj\MyProject.csproj.nuget.g.targets" was not imported by "C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\amd64\Microsoft.Common.targets" at (35,3), due to the file not existing.
I checked and the file does indeed exist.
Apart from being quicker to use, the reason I use dotnet new instead of creating the solution/project in Visual Studio is that Visual Studio complains about long paths and refuses to create projects that would output files with a path length over 259 characters, despite Windows 10 supporting paths that are thousands of characters long. The full path to the "missing" file is exactly 261 characters.
Is this caused by the max path issue, or is it something else?
Can someone assist with the following error which i am getting while building SSIS project using msbuild. I am having Visual studio 2015 in the machine. Using MSBuild 14.0
"*
error MSB4041: Th e default XML namespace of the project must be the
MSBuild XML namespace. If the project is authored in the MSBuild 200 3
format, please add
xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the
element. If the proje ct has been authored in the old 1.0 or
1.2 format, please convert it to MSBuild 2003 format.
*"
I have gone through some articles online but couldn't find solution with this scenario.
*" I have gone through some articles online but couldn't find solution with this scenario.
I'm afraid the answer is negative. For now this scenario(build SSIS project using msbuild) is not supported.
Someone has post this issue in DC forum, see Support SSIS, SSRS, SSAS in MSBuild. So if you're trying to use azure devops for CI/CD process, please vote and track this issue to get notifications when there's any update. And if you're using other tools for CI/CD process, I suggest you open a new feature request to support SSIS building for stand-alone msbuild tools in local machine.
And here're two workarounds which may help:
1.Since you have VS2015 installed, instead of msbuild command, you can try using devenv command.
For VS2015, we can find devenv.exe and devenv.com in path C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE. Both devenv.exe and devenv.com works for this, but note: Using devenv.exe directly prevents output from appearing on the console.
So devenv.xxx ... xxx.dtproj /build can work to build the SSIS project.
2.We can find binary(Microsoft.SqlServer.IntegrationServices.Build.dll) of the SQL Server Data Tools in C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE. Then we can use msbuild UsingTask element to call the tasks defined in that assembly.
The core is to call DeploymentFileCompilerTask task for SSIS build in our custom msbuild target after defining this statement:
<UsingTask TaskName="DeploymentFileCompilerTask" AssemblyFile="C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.SqlServer.IntegrationServices.Build.dll" />
More details please refer to here and here.
Update:
If we have several Database projects and SSIS projects in same solution. Using command like devenv.com xx.dtproj directly will actually build all projects.
So I suggest we use command in this way:
Open Developer command prompt for VS
cd to solution directory
use command: devenv.com SolutionName.sln /Build Development /Project SolutionName\xxx.dtproj /ProjectConfig Development
This will only build the SSIS project actually.
In addition: If you see the message The project 'DatabaseProjectName.sqlproj' will close once model building has paused. If it doesn't affect your build, just ignore it. After my check if won't actually build Database project(the output of database project is empty) if we use command above.
I have a solution created with VS2013 with this projects:
WebApp (Asp.net mvc5 web app)
Common (c# library project)
The solution is versioned on server TFS2013.
I Create and edited a build definition for my solution where i want create 2 build using Release and Debug configuration.
I have configured build definition like this article because i want tranform Web.Config
When i add MSBuild this arguments in my Team Build definition:
/p:DeployOnBuild=true /p:UseWPP_CopyWebApplication=True /p:PipelineDependsOnBuild=False
Now i have this error:
(PackageUsingManifest target) ->
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets(3883,5): error : Web deployment task failed.
(Unknown ProviderOption:DefiningProjectFullPath. Known ProviderOptions are:skipInvalid.)
If i remove the MSBuild argument it works.
QUESTION: What's could be configured wrong?
I discovered that on my local machine there was Visual Studio 2013 Update 5 while on the server TFS there was Visual Studio 2013 RTM (no update).
I resolved with a update of Visual Studio 2013 at last version (Update 5) on server where is installed TFS.
I have to enabled diagnostic mode of MSBuild project build output verbosity to see this:
1>Done executing task "EnableExtension" -- FAILED. (TaskId:81)
1>Done building target "DeployVsixExtensionFiles" in project "myextension.csproj" -- FAILED.: (TargetId:93)
...
1>Build FAILED.
1>
1>Time Elapsed 00:00:01.27
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========
My problem is I cannot debug the Visual Studio extension package I'm working on, as the build output says something has failed. What's wired, the obj and bin folders with all content inside (including vsix package), has been created. I don't really know what special I've changed, because few hours ago everything was fine.
How can I investigate what has gone wrong ?
Btw: I'm using VS 2012 Premium Update 1
EDIT:
I remembered what I've done. While being in debug mode, I entered Tools -> Extensions and Updates, and uninstalled my currently debugged extension (without restarting VS after that operation). Further attempt of debugging (F5 after CLOSING Experimental Instance of VS) results in this mysterious build behavior.
My current workaround I've come up with after some time is to change the display name of the extension package in the source.extension.vsixmanifest file:
<Metadata>
...
<DisplayName>Change this name to sth else and press F5</DisplayName>
...
</Metadata>
Nothing else needs to be changed (unfortunately reversion to old name still fires this error, but at least developing and debugging can be continued).
UPDATE:
I've checked the windows registry for such problematic name, and found following PendingDeletions key:
HKEY_USERS\S-1-5-21-1832937852-2116575123-337272265-599953\Software\Microsoft\VisualStudio\11.0Exp\ExtensionManager\PendingDeletions
Under this key there is value pointing at my extension I've previously uninstalled (while being in the debug mode):
C:\USERS\G_159\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\11.0EXP\EXTENSIONS\JAROSLAW WALISZKO\MYEXTENSION\1.0\
Removal of this entry fixes that case.
Davide Icardi commented:
Another solution is to manually open the Visual Studio experimental instance. Starting it caused all the pending extensions to be deleted automatically.
To start the experimental instance, run this command in a developer command prompt:
devenv.exe /RootSuffix Exp
Update: I'm dumb - after installing the VS 2013 SDK, there's a shortcut to start the experimental instance in the Visual Studio 2013 folder of the Start menu.
I get following error everytime I try to create a new Test Project:
Microsoft Visual Studio
Failed to get service ITestToolSettingsManager.
OK
I am currently running Visual Studio 2010 Ultimate with Feature Pack 2 on Windows 7 Ultimate 64-bit.
I have also tried following with no avail:
Run VS under admin mode
Reset VS settings by going to Tools --> Import and Export Settings
Run "devenv \setup" --> this fails
Run "devenv \InstallTFSTemplates"
Run "devenv \ResetSettings" --> this fails
Your help in resolving is much appreciated.
Kind regards,
HG
Probably same deal I had File => new project test projects Fails.
Installed Templates => Visual C# => Test => Test Project
works
found answer at
http://social.msdn.microsoft.com/Forums/en-US/vsunittest/thread/8739096e-afb3-4760-baeb-ae707fb3ab09