I have a Visual Studio with several projects inside of it (APIs, etc).
I want to add a Preact project to this solution, so I'm available to launch all of them at the same time.
How can I make a Preact project using Visual Studio 2022?
I can generate a React project, but is it possible to do the same for a Preact one?
If so, how do I have to do it?
Visual Studio has no menu item for creating a Preact project, no. You can create one using whatever tools you'd like (preact-cli or wmr are potential first-party options, but you're free to use whatever you'd like) and then you can add the run/build configurations to your IDE, same as any Node script.
Related
Developers use the Visual Studio (VS) GUI to develop their solutions and get their projects all building using a solution file (.SLN). The build teams using vNext then have to automate those builds using MSBuild instead of devenv.exe (the Visual Studio executable file). This is a serious and chronic problem because not only is MSBuild incapable of building several project types, but the build order is defined in a completely different, and complex, way.
Some Microsoft advice (https://learn.microsoft.com/en-us/archive/blogs/msbuild/incorrect-solution-build-ordering-when-using-msbuild-exe) is to switch to explicit dependencies in each .*proj file and remove all dependency specifications in the .SLN file. This sounds like a person who has never worked in a relatively powerless build team trying to get development teams to:
do a lot of what they perceive as time-wasting extra work and to
change how they do things
What build teams need is a way to automate whatever VS allows dev teams to build. If VS is given a SLN to build, then a vNext build needs to be able to use that same SLN in the same way. Instead vNext currently only offers MSBuild as the build tool. MSBuild has many more options than devenv, so that would be great, IF it could be made to use the SLN to govern dependencies in the same way as VS, and would be upgraded to build all the same project types.
There have been prospective efforts, referenced by PatrickLu-MSFT at Build project using devenv.exe in TFS 15RC1 Build Server, to enhance a vNext build step to allow devenv to be used instead of MSBuild, but those efforts seem to have been dropped.
Maybe someone has developed a custom vNext build step to build using devenv?
Here is an existing extension you can reference, which provides a build task in your TFS/VSTS instance that will allow you to build your projects using DevEnv.com (Visual Studio):
https://marketplace.visualstudio.com/items?itemName=mmajcica.devenv-build
If you want to automatically use TFS/DevOps build whatever solution files our development teams get working using Visual Studio, you could set CI trigger in build pipeline, when the solution build successfully on local, you can check in/commit the changes, and trigger TFS/DevOps builds.
I have some merge module projects created using advanced installer. I need to integrate them with visual studio. I have done same for MSI projects and they work fine. but I don't know how to achieve continuous integration for MSM using Visual Studio.
Advanced Installer extension for Microsoft Visual Studio allows to create Advanced Installer Projects for Visual Studio. Each such project is a container that can include a single .AIP file.
The Visual Studio Solution can include one or more Advanced Installer Project for Visual Studio, in accordance with your needs.
Note that you need to remove the default project that is created when adding a new Installer Project to the .sln and add the existing project, the project that builds the .msm package.
edit
Indeed, you are right. It was a misunderstanding on our end.
On my machine I have several extensions installed side by side. One of these extensions also supports the build of a merge module project type.
We do not officially support this yet. The option to build other project types (e.g. Merge Module Project, Updates Configuration Project) with our VS extension will be available in a future version of Advanced Installer. I will let you know when we will add support for this.
Until then, you can use a build event as a workaround to build the Merge Module Project within the Visual Studio project.
To build the .msm project you can use a command line as described below:
http://www.advancedinstaller.com/user-guide/command-line.html#build-project
The command line can be something as below:
AdvancedInstaller.com" /build "$(SolutionDir)Merge module sample.aip"
I have seen this:
Running two projects at once in Visual Studio
But I have another problem.
My solution had many executable projects.
Maybe I can allocate them into different groups.
For each group, It has a specific one or more startup projects.
So how can I configure it with Visual Studio 2017?
(Could I making some configuration in the project properties?)
You can use the SwitchStartupProject extension to select the startup project from a dropdown and switch between multi-project startup configurations.
Visual Studio 2013 with update 4 does not show a shared project template. I only have the Xamarin forms project templates. I just installed a fresh update of Xamarin this morning. Based on what I've found so far, this used to be an issue with VS update 2. Any idea on how to get shared project template to show up?
From Xamarin Support:
No, there's no optional bits missing. I think Visual Studio Update 4
removed the shared project template. It's a Microsoft template, not a
Xamarin one. You can still create a Xamarin.Forms app with a Shared
Project (that's our template), but they no longer allow you to create
an independent shared project.
So, three ways to create one now if you are using Visual Studio 2013:
1) Switch to Xamarin Studio and create it there and then close it and
reopen the solution in VS. VS will recognize the project, it just
doesn't have a template to create it anymore. This is probably the
easiest approach.
2) Install the "Shared Project Template" from the Online templates -
this is a 3rd party template; I've not tried it but if you want to
stay in VS and have the template, it's worth a shot.
3) Create either a Universal Windows Store app (which uses a Shared
Proejct), or a Xamarin.Forms app and then delete all the other
projects :)
Alternatively, Visual Studio 2015 (currently in CTP); last time I
checked, it still has the project template - you can install that
side-by-side with VS2013 and use it as your IDE.
What is the best way to pre-compile a asp.net4 mvc3 website with all its view files using visual studio 2010?
I'm a little confused because MS provides multiple solutions that sound very similar.
Web Deployment Projects
http://blogs.msdn.com/b/webdevtools/archive/2010/05/26/visual-studio-2010-web-deployment-projects-rtw-available-now.aspx
Web Deployment Tool
http://www.microsoft.com/download/en/details.aspx?id=25230
or can I just do all this from the default VS2010 SP1 without additional addons?
Can someone clarify?
When you build or publish your project, the website is already compiled. Only the views are dynamically compiled. If you want your views to be compiled also, you can edit your web project file. Change this line:
<MvcBuildViews>false</MvcBuildViews>
to:
<MvcBuildViews>true</MvcBuildViews>
To be able to edit the project file within visual studio you have to unload the project first (right-click, Unload Project) and then right click the project again and choose Edit Project.
When you made the change, your views will be automatically be build also.
This is not something you want to do during development, build time significantly increases.