Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Isolated environment. Possible incorrect projects for MSBuild Properties ~ $(TargetFrameworkVersion:Metadata) #41

Closed
3F opened this issue Nov 20, 2017 · 2 comments
Closed

Isolated environment. Possible incorrect projects for MSBuild Properties ~ $(TargetFrameworkVersion:Metadata) #41

3F opened this issue Nov 20, 2017 · 2 comments
Labels
bug
Milestone
1.14

Comments

@3F
Copy link
Owner

3F commented Nov 20, 2017

Noticed from DllExport project:

$(pMeta = "Metadata")
...
Metadata .NET: $(TargetFrameworkVersion:$(pMeta))

may return Metadata .NET: v4.0 (1.6.0-beta2) and Metadata .NET: v2.0 (1.6.0-beta3)

When <TargetFrameworkVersion>v2.0</TargetFrameworkVersion> https://github.com/3F/DllExport/blob/20eb9db848f4ae4f730a311c1e22567b83ded629/Metadata/Metadata.csproj#L9
@3F 3F added the bug label Nov 20, 2017
@3F
Copy link
Owner Author

3F commented Nov 20, 2017

Seems problem only for Isolated env (CI, etc.), and probably because of this:

vsSolutionBuildEvent/vsSolutionBuildEvent/IsolatedEnv.cs

Line 263 in e6f5f68

if(eCfg == formatCfg(prop["Configuration"], prop["Platform"])) {

But anyway we need to replace this logic by new MvsSln project.

@3F 3F changed the title Possible incorrect projects for MSBuild Properties ~ $(TargetFrameworkVersion:Metadata) Isolated environment. Possible incorrect projects for MSBuild Properties ~ $(TargetFrameworkVersion:Metadata) Nov 20, 2017
@3F 3F added this to the 0.12.12 milestone Aug 4, 2019
@3F 3F closed this as completed in 969be9c Sep 21, 2019
@3F
Copy link
Owner Author

3F commented Sep 21, 2019

Confirmed an fixed status after MvsSln integration #53

Verified via the same old changes:
https://github.com/3F/DllExport/releases/tag/v1.6-beta2

3F added a commit that referenced this issue Sep 26, 2019
@3F
Public release of vsSolutionBuildEvent 1.14
16ee135 
* NEW: Integration with MvsSln project. v2.4 PR #53.
       Replaces processing from IsolatedEnv/MSBuild/+ and fully removes our old parser.
       Finally it fixes lot of bugs (such as: #42, #41, #40,..) and also improves performance.
       https://github.com/3F/MvsSln

* NEW: Open Source independent script engines under the MIT License. Issue #55.

* NEW: Integration with E-MSBuild project. v1.14. Part of PR #56.
       Advanced Evaluator of MSBuild scripts with user-variables support through Varhead and more.
       https://github.com/3F/E-MSBuild

* NEW: Integration with SobaScript -- an Extensible Modular Scripting Programming Language.
       Part of PR #56.
       https://github.com/3F/SobaScript

* NEW: Included SobaScript Components:
       Z.Core: https://github.com/3F/SobaScript.Z.Core
        * ConditionComponent
        * EvMSBuildComponent
        * UserVariableComponent
        * TryComponent
        * CommentComponent
        * BoxComponent

       Z.Ext: https://github.com/3F/SobaScript.Z.Ext
        * SevenZipComponent
        * NuGetComponent
        * FileComponent
        * FunctionComponent

       Z.VS: https://github.com/3F/SobaScript.Z.VS
        * DTEComponent
        * OwpComponent
        * BuildComponent

* FIXED: Possible "Can not load 7-zip library or internal COM error"
         When using x64 instance. Issue #38.

* FIXED: Possible "An equivalent project is already present in the project collection."
         Issue #42.

* FIXED: Possible incorrect projects for MSBuild Properties
            ~ $(TargetFrameworkVersion:Metadata) Issue #41.

* FIXED: Failed getting project from EnvDTE. Issue #40.

* CHANGED: Increased performance when evaluating data and scripts.

* CHANGED: Updated 7z.Libs 19.0.1.

* CHANGED: Updated AvalonEdit 5.0.4

* CHANGED: Updated Microsoft.VisualStudio.Shell.15.0 15.9.28307

* CHANGED: SDK15 packages only:
           Updated Microsoft.Build & Microsoft.Build.Framework 16.0.461

* CHANGED: Updated EnvDTE 8.0.2

* CHANGED: Updated EnvDTE80 8.0.3

* CHANGED: Updated Newtonsoft.Json 12.0.2

* CHANGED: Updated Microsoft.VisualStudio.SDK.EmbedInteropTypes 15.0.27

* CHANGED: StreamJsonRpc 2.0.208

* CHANGED: System.ValueTuple 4.5.0

* CHANGED: NuGet package `vsSBE.CI.MSBuild` is obsolete. Please use new:
           https://www.nuget.org/packages/vsSolutionBuildEvent
           Also new 'tools\' folder instead of 'bin\'.

* KNOWN: Possible Failed Project.Pre/Post-binding: 'Object reference not set to an instance of an object.'
         Issue #43.
         Please enable debug mode, we're waiting for your reports.

* KNOWN: Known problem for VS2019. Build can be started before activation of our plugin.
         This is a feature of the modern VS platform with lazy loading of all plugins.
         Solution:
         Just attach once our [status panel] and this will always activate our plugin before start.

* KNOWN: Known problem when deactivated [Status Panel] from `View` - `Other Windows`.
         Incorrect identifier in previous version produces wrong tool.
         Solution:
         Just close this panel. Then, open it again from `View` - `Other Windows`.

* NOTE: Please note. New releases has been migrated from SourceForge to GitHub Release Page:
        https://github.com/3F/vsSolutionBuildEvent/releases
        https://vssbe.r-eg.net/Downloads/

* NOTE: Here is about SDK10 / SDK15 packages:
        https://vssbe.r-eg.net/doc/Usage/#sdk10--sdk15-versions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.14
Development

No branches or pull requests
1 participant
@3F