All the features and updates in this blog post are available in our latest version.
- Npm package management is available to help you manage your dependencies, and it will be discussed in detail in a later section.
Code Editing Experience
Compatibility with VS Code Debugging
- Improving helping to get your apps to Azure easier with continued integration with ASP.NET apps
Please share your feedback with us so we can better tailor our efforts to the needs of our community of developers.
Support for Svelte SPAs!
I think that’s a fabulous idea! Any step taken towards helping help people getting started with Visual Studio is a step in the right direction.
Is there any plan to improve the njsproj format ?
– moving to project SDK format
– improving the vstest integration.
we have use it to do some integration testing with our product and we are seeing some shortcoming on the vstest integration, mainly the fact that the filterig is not working which means we cannot use the vstest feature to restart a failed tests or distribute them.
Hey Frederic, thank you so much for your reply. We will be directing njsproj usage to esproj. The migration tool from njsproj to esproj will be available in 17.7 Preview 1. A tutorial on how to migrate will be published. Stay tuned!
Dear @Jiayan, I may have miss, is ejproj unit tests integated with VSTets ? I didn’t see any sample with unit tests with Mocha integrated into AzDO (vstest task?)- sorry if I missed that
It’s not integrated with VSTests I believe. If you would like to run unit tests with Mocha integrated into AzDO, you might consider using npm and include that as part of your AzDO pipeline. Please let us know if that works. Thanks!
I am glad to see the front end development experience improving in Visual Studio but I am a bit sad to see that you are not using latest recommendations for each framework. To create Vue projects, the official recommandation is to use the create-vue package and not the vue-cli anymore. For react applications the new documentation recommandation for new projects is to use a framework (like nextjs) or to to use react with vite or parcel.
For Vue new project creation, we are working on to change it to the create-vue package (using Vite under the hood). For React, from your use case, do you use a production framework or do you create react project using vite or parcel? Thanks!
Unfortunately, it looks like the new preview React template is using the unsupported create-react-app tool. Can this be updated to use an approved approach? The React team considers that tool dead and deprecated. It would be more helpful to see ViteJS used instead.
In my opinion you and Alexandre are right, this should be updated. Specially because CRA is not the recommended for new projects i hope they fix it.
Sure. Can you explain why would you prefer ViteJS over others in terms of new project creation? Thanks!
because it‘s so fast and simple
ViteJS seems to be best option for a direct CRA replacement. I’d rather use extensions through ViteJS than the clunky custom cert and proxy code in the VS template. We’re also not interested in using NextJS at all with our current or future SPA projects.
This project type is very useful, thank you for adding it.
Thank you so much for your comment. We are looking for ways to be more inclusive to different tooling options. To solve the specific npm install problem, you can add false in the first PropertyGroup in the project file (.esproj).
Ah, indeed, I can see now that in newest SDK versions (starting from 0.5.78-alpha) the target is now named “RunNpmInstall” and can be turned off using the “ShouldRunNpmInstall” property. In our projects we are using SDK 0.5.45-alpha (which I suppose was the current version at the time those projects were created), where the target had no such condition. Thank you for pointing me in this direction.
However, I think that even after upgrading to the newest SDK I will keep overriding the target (at least for the time being) instead of disabling it, because I do like the package install being performed automatically when needed. I only need to replace “npm install” with “pnpm install” (and adjust the value of the NpmInstallCheck property to point to pnpm-lock.yaml).
How open a typescript project in Visual Studio 2022 Preview on Macbook?
In the window ‘New Project’ -> Typescript project only does not exist.
I’d like to be able to work on the same typescript and assets files using either Visual Studio or/and Visual Studio Code. What I miss today is a Visual Studio .proj file that would do nothing (no node.js run) but run the scripts in package.json, exactly what I do with Visual Studio Code, but I like Visual Studio better (faster, better, and it’s my main dev tool). For example in Visual Studio Code, I use “parcel watch …” to automatically update my resulting files (from typescript), and I use Visual Studio Code’s Live Server on a the same resulting root html file. I have tested various Visual Studio (2022 17.6) projects today and I don’t seem to find what I’m looking for.