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

Consider creating a Nuget package. #45

Closed
nosami opened this issue Mar 27, 2015 · 5 comments
Closed

Consider creating a Nuget package. #45

nosami opened this issue Mar 27, 2015 · 5 comments
Labels

Comments

@nosami
Copy link

nosami commented Mar 27, 2015

I'd like to use Microsoft.Build.Evaluation both for parsing project files and writing back to them in OmniSharp https://github.com/OmniSharp/omnisharp-roslyn

Please could you consider creating a nuget package so that I can easily consume this code? Thanks.

@lilith
Copy link

lilith commented Mar 28, 2015

A nuget package to contain msbuild.exe would also be quite nice. Most CI scripts call paket restore or nuget restore before invoking msbuild anyway; no reason we can't install it and change an environment variable to point to it.

@ctaggart
Copy link

ctaggart commented May 3, 2015

A nuget package for Microsoft.Build package would be awesome! I can't figure out a way to reference the latest Microsoft.Build assembly in the GAC from F# interactive. Solving that would help me fix a SourceLink issue. I always end up with 4.0.0. A nuget package would allow me to simply reference the file which would be perfect.

@ctaggart
Copy link

ctaggart commented May 7, 2015

I went ahead and published my branch here with three of the assemblies I needed:
https://www.nuget.org/packages/SourceLink.MSBuild/

The build was created on AppVeyor using this build script. All tests pass.
image

I'll put together a blog with more details. I'm mentioning this here in case others can use this NuGet package or want a build script.

@ghost
Copy link

ghost commented May 16, 2015

@ctaggart, please consider sending a PR to this repo, so everyone depend on the same updated package.

@akoeplinger
Copy link
Member

A PR for NuGet packages was already opened here: #95

@ghost ghost mentioned this issue May 17, 2015
radical added a commit to radical/msbuild that referenced this issue Mar 24, 2018
…th (dotnet#44) (dotnet#45)

When running on !windows, if a resx contains a fileRef like ..

```
  <data name="TextFile1" type="System.Resources.ResXFileRef, System.Windows.Forms">
    <value>..\Resources\TextFile1.txt;System.String, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089;Windows-1252</value>
  </data>
```

.. with the path containing backslashes, then we end up treating the whole
thing as filename and thus subsequent checks for file changes etc fail. This
causes the resx to be processed every time `GenerateResource` task is run, which
can cause costly rebuilds.

Issue: mono/mono#7184
(cherry picked from commit dfb274e)
@AR-May AR-May added the triaged label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants