I am writing all of my back-end code in F# & C# and I have them in a Visual Studio Solution with Git Set up etc. I have been wanting to do some front-end work using the Dev Extreme Framework & related Components. I separately installed a devextreme App using the command line ( outside of Visual Studio ) using the Method Here, Vuejs Version 3.
Everything works fine if I run it within the command line but I would like to edit the pages etc in Visual studio.
The only way I could get it into Visual Studio was to Create a basic Vue.js application in Visual Studio - rip all the files out except for the project file and add my other files I created using the link above.
Now - I am getting over 500 error within visual Studio - even though I can run the app in the PowerShell window in Visual Studio. I have excluded the node_modules directory but it looks like most of the errors are in that directory.
The solution looks like this:
I feel like I am fundamentally missing something.
Related
I have never used Visual Studio for Mac before (not VS Code). I want to try out a tutorial to learn VS Studio by making a simple react app. I've tried creating a new project with VS studio, and then running npx create-react-app in the folder of the new project, but VS studio doesn't see the new folder. I've also tried opening the folder created by create-react-app , but VS Studio refuses to recognize it as a volder it knows, it's greyed out. Thanks for helping out on this basic beginning step.
Microsoft's documentation on using React in Visual Studio (see "Applies to" section at top of page) implies that using Visual Studio for Mac with React at the very least does not work with React the same way that Visual Studio (for Windows) does and may even suggest that some functionality is not be supported.
You can create a Visual Studio Project of template Web and Console -> React js and it will create a react app in the ClientApp folder of the project which you can work on. It will have a asp c# component in the project but that will be for in case you want to write server side which you can ignore for your development (if not needed). PS: I do not think we can create and run Node.js server side in visual studio ... atleast I am not aware how! being Microsoft i presume they will want you to write server side in ASP .NET
I am using Visual Studio 2017 on Windows 10 with the official UWP sample code.
There is a UWP sample called basicinput that runs as a release build within the Visual Studio IDE without a problem.
My problem is:
when I attempt to run the release basicinput.exe executable by a mouse click (outside of the Visual Studio environment) I get an error saying that some DLLs names of the form vs*.dll can't be found.
I did a search for those .dlls and tried moving them to same folder as basicinput.exe, but then the application just hung.
What don't I understand?
What am I doing wrong?
As #Chuck-walbourn says, your application will appear in the Start Menu. If you want to deploy it to another computer (that doesn't have VS installed) you will need to create AppX packages using the menu item Project -> Store -> Create App Packages.... If you need more help with that. see the MSDN docs.
If you want to run your app from the command-line or from the Win+R dialog (with a simple name like foo.exe) you can create an appExecutionAlias for your application.
I have a new .net Core 2.0 Web API project (In Visual Studio 2017 Version 15.3.5) where I can´t build the solution if I add a new database project.
error MSB4019: The imported project "C:\Program Files\dotnet\sdk\2.0.0\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I have tried all kinds of solutions
Installed almost everything missing from the Visual Studio Installer
Installed Visual Studio Build Tools 2017
Repaired Visual Studio
Without luck I tried to find Microsoft.Data.Tools.Schema.SqlTasks.targets file on C:\ to the add reference to it in the project file (I then don´t know if that works while building the solution in VSTS).
So why can I add a database project to a normal API project and everything works just fine but not to a .net core one?
Do database projects not work with .net Core? I have searched for information on this but sorry I just can´t find it.
I´m not sure what to do. Hope somebody can help.
Ok I managed to find the Microsoft.Data.Tools.Schema.SqlTasks.targets file on my computer.
I then needed to unload the project and edit it
There I changed this line
<SSDTExists Condition="Exists('$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets')">True</SSDTExists>
to the hardcoded path of my file
<SSDTExists Condition="Exists('C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets')">True</SSDTExists>
And now it builds on my computer and on VSTS.
But why this is like this I don´t know.
I was having the exact same issue building a SQL Server project on an Azure DevOps CI/CD pipeline, and locally on VS Code. On Azure DevOps none of the pre-built build tasks would work for me, and locally I could only compile the SQL Server project on Visual Studio, which was annoying. Your solution didn't work for me, after doing what you suggest, I would get a .dll missing error, related with the first error.
I solved this by avoiding to add a SQL Server project to the solution.
I achieved this by using an MSBuild SDK, capable of producing a SQL Server Data-Tier Application package (.dacpac) from the set of SQL scripts. By adding this second project to the solution, I managed to continue taking advantage of linking the project to a live database through SQL Server Object Explorer on Visual Studio. I gave a more detailed explanation about my implementation in this answer.
We are attempting to upgrade our rather old TFS environment from TFS2008 to TFS2015. The upgrade of the server and database is not a problem and is fine.
The issue is our build machine. This is still a Windows 2003 Server that is running Visual Studio 2010 and VB6. We still have a need to use this build machine to build legacy VB6 projects. We have installed the TFS2010 XAML build controller on this server and successfully connected it to our test TFS2015 server. However when we try to run a Xaml build, (any Xaml build regardless of whether it builds VB6 or .NET) we get the following error message almost straight away.
TF900560: Could not start build: Cannot set unknown member 'Microsoft.TeamFoundation.Build.Workflow.Activities.TfsBuild.TargetsNotLogged'.
The XAML build are using the 'UpgradeTemplate.xaml' template and using the TFSBuild.proj we used under Visual Studio 2010.
We have a also set up a TFS2015 build controller on another (Server 2012) machine and that successfully starts the build process. However, our VB6 projects use a lot of third party components that will not install on Server 2012 so we can't use that.
Has anyone ever set up this kind of arrangement before? Is there anything we are missing or are doomed in this scenario? Obviously, we'd like to move away from VB6 apps, but that is not possible in the medium term.
I've written a c# program that builds *.csproj and *.vcxproj using Microsoft.Build.Evaluation. It works great on both project types if I compile and run it from inside Visual Studio 12. But if I run the exe directly (outside of Visual Studio) I get the example error message below. The error occurs only for vcx projects; c# projects continue to build just fine
Question: Why am I getting this error? Why does my program work fine for both C# and vcx projects when run from within VS12, but fails, but only for vcx projects, when run outside of VS12?
Please don't chastise me for not using MSBuild.exe. My orders were to programmatically build C# and vcx projects using Microsoft.Build.Evaluation.
Code:
using Microsoft.Build.Evaluation;
...
Project proj = new Project("MyCppProject.vcxproj");
proj.Build(logger);
Runtime Error:
Building MyCppProject
Project "MyCppProject.vcxproj" (default targets):
VCMessage:
ERROR C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(518,5): Specified platform toolset (v110) is not installed or invalid. Please make sure that a supported PlatformToolset value is selected.
Done building project "MyCppProject" -- FAILED.
One solution is to force the Visual Studio version as an environment variable prior to loading and building the project:
using Microsoft.Build.Evaluation;
...
Environment.SetEnvironmentVariable("VisualStudioVersion", "11.0")
Project proj = new Project("MyCppProject.vcxproj");
proj.Build(logger);
Visual studio maintains platform tool sets list supported for the version of Visual studio you are currently running for example on my machine I have VS 2008, 2010 and 2012
Now suppose when I install Visual Studio 2013 which has a Platform Toolset version of V120. What happens, is that the project saves this in its corresponding XML files in the format (vcproj, vcxproj, vcxproj.filter.user files).
now this valus is not known to VS 2012 so it complains when opened in VS 2012.
Similarly for opening VS 2012 project in VS 2010, as in your case and so on.
Solution:
To fix this issue, Open you solution file in notepad++.
Make these 2 changes
1) Replace
Format Version 12.00
with
Format Version 11.00
2) Replace
Visual Studio 2012
with
Visual Studio 2010
Then open the file again in visual studio and rebuild solution.