(Replacing message template with parser tag) |
No edit summary |
||
| Line 9: | Line 9: | ||
Including builds for .net core and .net standard https://www.nuget.org/packages/MDrivenCorenetStandard/ | Including builds for .net core and .net standard https://www.nuget.org/packages/MDrivenCorenetStandard/ | ||
=== .netFramework48 strategy === | |||
MDriven will focus on the Long time supported versions of .net - currently the latest is .net8. | |||
We still have internal need to maintain .netFramework48 versions due to the VisualStudio2022-extension for MDrivenFramework builds with that version. We have however been made aware of that VisualStudio2022 can handle extensions built with .net8. This is something we will investigate rather soon. | |||
Currently we think it is very easy to switch from .netFramework48 to .net8. The main work seems to be around the project file itself - the format has changed and it now includes everything in the folder by default rather than needing explicit entrys as before. | |||
MDriven are not aware of any limitations to our .net8 versions vs .netFramework48 versions - except when it comes to WCF which we have decided to not move forward with and instead focus on WebApi as communication infrastructure. | |||
=== MDrivenServer Core === | === MDrivenServer Core === | ||
Revision as of 09:39, 13 September 2024
MDriven Turnkey comes in a new edition for dotnet core. Currently, we build .net5.
The current version is published in this XML: https://mdriven.net/PublicDownloads/MDrivenTurnkeyOnCoreVersion.xml
The download is found in a link formed like this: https://mdriven.net/PublicDownloads/MDrivenTurnkeyCore_<TheVersion>.zip
We are also publishing builds to NugetProject.
Including builds for .net core and .net standard https://www.nuget.org/packages/MDrivenCorenetStandard/
.netFramework48 strategy
MDriven will focus on the Long time supported versions of .net - currently the latest is .net8.
We still have internal need to maintain .netFramework48 versions due to the VisualStudio2022-extension for MDrivenFramework builds with that version. We have however been made aware of that VisualStudio2022 can handle extensions built with .net8. This is something we will investigate rather soon.
Currently we think it is very easy to switch from .netFramework48 to .net8. The main work seems to be around the project file itself - the format has changed and it now includes everything in the folder by default rather than needing explicit entrys as before.
MDriven are not aware of any limitations to our .net8 versions vs .netFramework48 versions - except when it comes to WCF which we have decided to not move forward with and instead focus on WebApi as communication infrastructure.
MDrivenServer Core
Now we also publish the MDrivenServer compiled with .NetCore 3.1 which is located here: https://mdriven.net/PublicDownloads/MDrivenServerCore_<version>.zip.
The current version is found here: https://mdriven.net/PublicDownloads/MDrivenServerOnCoreVersion.xml
Read more about using the full MDrivenStack locally here: LocalServers
Read more on hosting MDrivenServerCore in IIS
NuGet
We also publish to Nuget: https://www.nuget.org/profiles/MDriven
Visual Studio
Visual Studio has been given new templates to help you get started with MDriven on .net Standard/Core.
