Drop MSBuild

[3F]

This question has been raised a very long time. As I already mentioned:

Modern #MSBuild assemblies are much more closely integrated with #VisualStudio and much more difficult to maintain independently

ie. without VS/dotnet sdk dependencies.

We need to consider more independent implementation as possible. At least for an alternative way.

Why

• https://github.com/3F/MvsSln/wiki/Advanced-Features#about--possible--problems
• https://github.com/microsoft/msbuild/issues/3581
• https://github.com/3F/MvsSln/pull/21
• https://github.com/3F/MvsSln/issues/1
• https://github.com/3F/MvsSln/issues/2
• https://github.com/3F/MvsSln/issues/4
• https://github.com/3F/MvsSln/issues/5
• https://github.com/3F/MvsSln/issues/24
• https://github.com/3F/MvsSln/issues/25
• https://github.com/3F/DllExport/issues/143
• https://github.com/3F/DllExport/pull/123
• ...

How

Either basing on original https://github.com/microsoft/msbuild (MIT) or from scratch.

What

• Compatible Evaluator engine.
• Basic manipulation with XML nodes.

Where

At least for public:

• MvsSln
• E-MSBuild
• .NET DllExport
• SobaScript
• vsCommandEvent
• vsSolutionBuildEvent
• ...

[3F]

Something good is almost here; I started new project https://github.com/3F/IeXod that should finally replace MSBuild where evaluating, manipulating, and other related data processing with project files (if we're talking strictly about MvsSln);

So, MvsSln 3.0 will be started at least after first stable IeXod release. Please test IeXod. 0.1 beta is just rolled out.