You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 17, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 17, 2025. It is now read-only.
Add NuGet package creation (with signing) to the CI configuration #10
@mlorbetske if you can get it producing a package as part of the official build, it'll be relatively simple to get it publishing on some nuget, like myget or nuget.org.
Activity
333fred commentedon Mar 31, 2017
@mlorbetske if you can get it producing a package as part of the official build, it'll be relatively simple to get it publishing on some nuget, like myget or nuget.org.
DustinCampbell commentedon May 2, 2017
FYI that I'm finally starting the work to get this into OmniSharp.
tintoy commentedon Sep 11, 2017
@DustinCampbell - are you saying you'll be extending OmniSharp to provide intellisense natively for MSBuild project files?
DustinCampbell commentedon Sep 11, 2017
I started looking at that at one point, but I'm no longer convinced that's the right approach.
tintoy commentedon Sep 11, 2017
No worries - I have built something that complements Omnisharp in the MSBuild department, just wanted to avoid duplication of effort :)
DustinCampbell commentedon Sep 11, 2017
FWIW, I do still intend to integrate something into C# for VS Code someday. There's just now enough hours in the day. 😀
tintoy commentedon Sep 11, 2017
Heh, no worries; when you do decide to have a go, perhaps we can pool our efforts.
Here's what I have so far:
https://github.com/tintoy/msbuild-project-tools-vscode
It's LSP-based so not directly dependent on VSCode (although it probably makes one or 2 VSCode-specific assumptions somewhere)...