What exactly is MSBee? How should I use it in addition to MSBuild to build web applications which are created in Visual Studio .NET 2003 and that target .NET Framework 1.1?
MSBuild Extras – Toolkit for .NET 1.1
“MSBee” is an addition to MSBuild that
allows developers to build managed
applications using Visual Studio 2005
projects that target .NET 1.1.
Take a look at the codeplex page:
http://www.codeplex.com/wikipage?ProjectName=MSBee
Also, look into upgrading the version of .NET/VS you are using. You're due...
Related
By default, Visual Studio 2022 Extension (Add-in) Project is on .Net Framework (not .Net 5 or 6). When I manually .csproj > PropertyGroup > TargetFramework XML value to net5.0, I run into a compile error.
Some of my projects are made with .Net 5 and it cannot be built with multiple targets (i.e. both .Net 5 and .Net Framework), which are needed to be referenced by my Visual Studio Extension project. Unfortunately, a .Net Framework project cannot reference a .Net 5 project, on the other hand, the vice versa can be partially available.
Is there any way of making Visual Studio Extensions with .Net 5 or later? If it cannot be done, how can I have my Visual Studio Extension project reference a .Net 5 based libraries(.dll)?
Visual Studio itself is currently a .NET 4.8 application, so you can't use .NET 5 stuff in it anywhere.
Visual Studio is adding support for out-of-process extensions, meaning that they run in a separate process from Visual Studio's main devenv.exe process, which runs on .NET Framework 4.x. That means the extension can be written using other technologies, such as .NET 6.
Blog post: https://devblogs.microsoft.com/visualstudio/the-future-of-visual-studio-extensibility-is-here/
Write your first extension: https://github.com/microsoft/VSExtensibility/blob/main/docs/new-extensibility-model/getting-started/create-your-first-extension.md
Out-of-proc extensibility: https://github.com/microsoft/VSExtensibility/blob/main/docs/new-extensibility-model/getting-started/oop-extensibility-model-overview.md
Out-of-proc UI: https://github.com/microsoft/VSExtensibility/blob/main/docs/new-extensibility-model/inside-the-sdk/remote-ui.md
I have a solution containing .NET Framework project - WPF application, frontend - and multiple .NET Standard projects - backend. I need to build the .NET Framework project, but to do it, I must build the .NET Standard projects, because the .NET Framework project references the .NET Standard projects.
Visual Studio Build and MSBuild throw errors like "'System' namespace doesn't exist" in the .NET Standard projects.
Net Core build fails to find some assemblies in certain Nuget packages, namely Prism and DevExpress.
How should I build .NET Framework WPF app that is referencing .NET Standard in Azure DevOps?
Thanks Levi Lu for his reply. It is the solution. Reposting it here:
"
I just used the Visual Studio Build task to build the solution. If you see above error, you can try setting the restoreNugetPackages: true of Visual Studio Build task.
"
I have several solutions that target some combination of .NET Standard 2.0 or .NET Core 2.1. I have the latest .NET Core 2.1 SDK installed.
When I build them via Visual Studio for Mac, I notice it is using the Mono build tools instead of dotnet such as csc.exe:
Target CoreCompile:
/Library/Frameworks/Mono.framework/Versions/5.16.0/lib/mono/msbuild/15.0/bin/Roslyn/csc.exe
Is there an option or some other property needs changed so that it can use the SDK instead of the Mono tools?
There is no option to use dotnet for building within Visual Studio for Mac. It uses msbuild. If you really want to do that you would need to bypass the built-in support and use of msbuild that VS Mac provides.
VS Mac uses msbuild that ships with Mono because it supports more target frameworks (e.g. Xamarin.iOS, Xamarin.Android) than the .NET Core SDK's MSBuild does. Note that VS on Windows takes a similar approach where it uses a desktop MSBuild to run builds and does not use dotnet build.
However Mono's MSBuild still uses the various MSBuild sdk target files that are shipped with the .NET Core SDK. There is an MSBuild sdk resolver that ships with Mono that allows the .NET Core SDK msbuild targets to be found and used.
Also note that Mono's MSBuild includes some parts of the .NET Core SDK so it can compile .NET Standard projects without needing the .NET Core SDK.
I am new to ASP.NET MVC applications and I'm building a web project in Visual Studio 2015. My project targets .Net framework 4.6. I want to know which version of ASP.NET MVC is installed with this version of the framework. I have browsed a lot and also looked for answers at the ASP.NET official website, but could not find the answer.
A relevant, but not specific, answer was found at:
https://softwareengineering.stackexchange.com/questions/157717/what-is-dependency-of-asp-net-mvc-on-net-framework-and-how-to-use-it-with-net
It would be great if someone could list the versions of ASP.NET MVC alongside the versions of the .Net framework they depend upon.
Try using Visual Studio 2017, because it is not dependent on the OS you are using or targeting.
As for your question, which version of MVC are you currently using, and what are the requirements for the project?
If you're building a website that uses Entity Framework or APIs, then I recommend using framework 4.6 and MVC 5 or Core.
According to MSDN:
Runtime Changes Runtime changes affect all apps that are running under
the .NET Framework 4.6 and that use a particular feature. Retargeting
Changes Retargeting changes affect apps that are recompiled to target
the .NET Framework 4.5, 4.5.1, or 4.5.2, or 4.6. They include: Changes
in the design-time environment. For example, build tools may emit
warnings when previously they did not. Changes in the runtime
environment. These affect only apps that specifically target the .NET
Framework 4.6. Apps that target previous versions of the .NET
Framework behave as they did when running under those versions.
I hope this helps you.
We have asp.net 1.1 framework application is in live environment with appx 200 users.
Which visual studio version is safe to use for maintenance?
We are not planning to migrate yet. I am using vs 2008 for developing a 3.5 application right now so not want to take the risk of visual studio conversion.
You can check with visual studio2005 version
Use Visual Studio .NET 2003 and MSDN Library of Jan 2006.
I think you can use any Visual studio once your project is targeting the correct framework. This Post talks you through installing aspt 1.1 on a windows 8 machine.