search

3F / vsSolutionBuildEvent

🎛 Event-Catcher with variety of advanced Actions to service projects, libraries, build processes, runtime environment of the Visual Studio, MSBuild Tools, and …
Other
79 stars 22 forks source link

MvsSln Integration. Back to parent. #53

Closed 3F closed 5 years ago

3F commented 5 years ago

Fixes #42 and more!

Will replace related processing from IsolatedEnv/MSBuild etc. and fully remove old parser.

3F commented 5 years ago

okay, I have some note...

Today I noticed bug with Environment.StartupProjectString. And 26fd0ec already contains fixes for this but I have no plan to add separately some patch into master because actually this was fixed as:

https://github.com/3F/vsSolutionBuildEvent/blob/26fd0ec76bf3b96c547fadd94df592b475648531/vsSolutionBuildEvent/Environment.cs#L180-L187

That includes processing via modern MvsSln! While temp native patch requires lot of additional steps because EnvDTE does not provide relative path, and moreover can't easily extract an unified project name, and we also need processing through IVsHierarchy and so on.

https://github.com/3F/vsSolutionBuildEvent/blob/26fd0ec76bf3b96c547fadd94df592b475648531/vsSolutionBuildEvent/Extensions/ProjectExtension.cs#L90-L93

https://github.com/3F/vsSolutionBuildEvent/blob/26fd0ec76bf3b96c547fadd94df592b475648531/vsSolutionBuildEvent/Environment.cs#L175-L178

Therefore, I will not waste time on additional irrelevant changes while this PR is actual for us. Just to do something later anyway :)

3F commented 5 years ago

Looks like vsSolutionBuildEvent now is completely integrated with MvsSln. Stable behavior after 5e3814fd07ff