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.

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

Drop MSBuild #23

Open
3F opened this issue Oct 15, 2019 · 1 comment
Open

Drop MSBuild #23

3F opened this issue Oct 15, 2019 · 1 comment
Labels
core enhancement env Active environment and its .vcxproj, .csproj, ... support
Milestone

Comments

@3F
Copy link
Owner

3F commented Oct 15, 2019

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

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:

@3F 3F added this to the 3.0 milestone Oct 15, 2019
@3F 3F added the env Active environment and its .vcxproj, .csproj, ... support label Oct 15, 2019
3F added a commit to 3F/DllExport that referenced this issue Nov 4, 2019
* NEW: Basic support for the netcore-based projects.
       Issues: #90, #67
       PR: #123

* CHANGED: Updated CoreCLR 3.0 IL Assembler 4.700.1
           https://github.com/3F/coreclr

* CHANGED: Updated Mono Cecil 0.11

* CHANGED: Updated MvsSln 2.5

* NOTE: You also need an updated manager to avoid problem
        when "Possible incorrect Sdk-based project types": PR #123
        3F/MvsSln#23

        Use it from official 1.7-beta release:
        https://github.com/3F/DllExport/releases/tag/v1.7-beta
        https://www.nuget.org/packages/DllExport/1.7.0-beta

        Otherwise you need provide manually msbuild instance
        that can process modern Sdk-types due to modern VS/dotnet sdk
        dependencies for netcore-based projects.

        For example, through hMSBuild https://github.com/3F/hMSBuild
        ```
        DllExport ... -msb hMSBuild
        ```

* NOTE: To upgrade configured version to 1.7 beta:
        ```
            DllExport -action Upgrade -dxp-version 1.7.0-beta
        ```

* NOTE: Please don't use beta releases in production!

* NOTE: Please report about something here: https://github.com/3F/DllExport/issues

* KNOWN: You can finally get another System.Object in modified assembly:
         #90 (comment)
3F added a commit to 3F/DllExport that referenced this issue Jan 31, 2020
* NEW: .NET Core based projects support.
       Issues: #90, #67
       PR: #123

* NEW: .NET Standard 1.1 and above targeting support.

* NEW: Implemented "Single + Double Inf/-Inf token patching" option.
       Related Issue #128.

* NEW: Implemented "Rebase System Object" option for our assembler.

        Helps to avoid possible "Invalid memory access" (JNA/Java). Issue #125.
        For C/C++ such as "Unhandled exception at ... (KernelBase)"

        https://twitter.com/GitHub3F/status/1201904821093187585
        Part of PR #123

* NEW: Implemented updater for wizard. Issue #109.

* NEW: Textual export of affected data to diag.

* CHANGED: Updated CoreCLR 3.1.0 LTS \ IL Assembler 4.700.2.
           https://github.com/3F/coreclr/releases/tag/ILAsm.4.700.2

           Includes an implemented `/REBASE` feature for related issue #125.

* CHANGED: New installation behavior through official NuGet.
           init.ps1 also adds optional copying of package data for our manager.

           Please note: This is not nuget support!
                        It just replaces known info-form that was in 1.6.x.

* CHANGED: New wizard layout for 1.7.

* CHANGED: Local scope when invoking .\DllExport manager in project files.

* CHANGED: Updated logic for an offline versions
            with optional converting to online if needed.

* CHANGED: Updated MvsSln 2.5.1
           https://github.com/3F/MvsSln/releases/tag/2.5.1

* CHANGED: Updated hMSBuild 2.3
           https://github.com/3F/hMSBuild/releases/tag/v2.3

* KNOWN: You can finally get another System.Object in modified assembly:
         #90 (comment)

* NOTE: You need an updated/modern manager to avoid problem
        when "Possible incorrect Sdk-based project types": PR #123
        3F/MvsSln#23

        Use it from official 1.7 release:
        https://github.com/3F/DllExport/releases/tag/v1.7
        https://www.nuget.org/packages/DllExport/1.7.0

        Otherwise you need provide manually msbuild instance
        that can process modern Sdk-types due to modern VS/dotnet sdk
        dependencies for netcore-based projects.

        For example, through hMSBuild https://github.com/3F/hMSBuild
        ```
        DllExport ... -msb hMSBuild
        ```

* NOTE: For command-line mode, To upgrade configured version to 1.7:
        ```
            DllExport -action Upgrade -dxp-version 1.7.0
        ```
@3F
Copy link
Owner Author

3F commented Jun 4, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core enhancement env Active environment and its .vcxproj, .csproj, ... support
Projects
None yet
Development

No branches or pull requests

1 participant