Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    George Tsiokos
    @GeorgeTsiokos
    Thanks again for this MsBuild integration - my build process looks much better thanks to this project!
    Herb Stahl
    @ghstahl
    just started looking at this. Is there a plan to let users configure in npm options. i.e. npm install --msvc_version=2012
    Kevin Mees
    @kmees
    hey. that's already possible by overriding the NpmCommand property. See https://github.com/kmees/MSBuild.NodeTools/blob/master/build/MSBuild.Npm.props
    Herb Stahl
    @ghstahl
    Thanks, works like a charm. I put the override at the end of the csproj.
    Kevin Mees
    @kmees
    Herb Stahl
    @ghstahl
    I am noticing a behavior on a solution where I have 4 project that I put in node tools. Just loading the solution makes visual studio 2013 come to a crawl, and I do notice a lot of activity with the "Event I/0 for V8 JavaScript" process. This makes me think that these MSBUILD tasks are firing on load. I haven't dug any deeper yet, but hoping you have noticed something similar.
    Herb Stahl
    @ghstahl
    Uninstalling node tools, did the trick, my project loads fast again. I am going to keep playing around with this, but it essentially killed VS2013
    Kevin Mees
    @kmees
    I haven't noticed any performance issues yet, but i'll have a look when i'm back home next week
    Luke Barnett
    @luke-barnett
    Hello
    Luke Barnett
    @luke-barnett
    should I be seeing output to the build window?
    Kevin Mees
    @kmees
    Yes, but you might need to increase the log output level in VS
    Diijon
    @diijon
    nuget install throws error 
    Install-Package : This collection is read-only.
At line:1 char:1
+ Install-Package MSBuild.NodeTools
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Install-Package], InvalidOperationException
    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
    Kevin Mees
    @kmees
    what version did you try to install?
    Diijon
    @diijon
    Version 0.4.3 since it was the latest version on the 27th. I immediately switched to manual install and everything worked. I see you bumped nuget yesterday (4/1). I'll try it when i get a chance
    Kevin Mees
    @kmees
    *nuspec
    yeah i fixed some neuspec dependencies in that release
    Kel
    @distransient
    Hey I'm running into a bit of an issue with the way nodetools is set up
    In my azure deployment, I'm bundling node.js as a nuget dependency, but the node.js nuget package doesn't keep an npm executable in its root directory like node.js normally does, I have to install it as a second nuget dependency
    however, nodetools is hardcoded to look for npm in the node.js directory. do you have any advice?
    ref: https://github.com/kmees/MSBuild.NodeTools/blob/af27f7c750456d618feacb2e714139f10ed419a2/build/MSBuild.Npm.targets#L8
    Kel
    @distransient
    also, the properties I'm passing to nodetools in my csproj are
        <LocalNodePath>$(MSBuildProjectDirectory)\..\packages\Node.js.0.12.0</LocalNodePath>
    <LocalNodeModulePath>$(MSBuildProjectDirectory)</LocalNodeModulePath>
    Kel
    @distransient
    I also had tried to use .bin, which is where both node.js and npm.js package's executable cmd files are stored but MSBuild.Node.targets checks to see if !Exists('$(LocalNodePath)') and .bin is already set to a variable (at least that's what I think that conditional does? it errors out at the least with Invalid local node path)
    Kel
    @distransient
    I fixed it! that was returning that .bin wasn't existing because it wasn't part of the project, so when deployed, it wouldn't be seen on azure (I wasn't including it because it's a build directory for my packages right? that msbuild would handle for me right? WRONG!). So .bin needed to be added to the project and I could use it
    but to use MSBuild.NodeTools with local nuget versions of Node, Gulp, and Npm, do
    <LocalNodePath>$(MSBuildProjectDirectory)\.bin</LocalNodePath>
<LocalNodeModulePath>$(MSBuildProjectDirectory)\node_modules\.bin</LocalNodeModulePath>
    Long Sigh that was really something to figure out. thanks for the tool! hope my troubles might make someone else's life easier in the future
    Ezequiel Calderara
    @ironicnet
    Hi guys
    Ezequiel Calderara
    @ironicnet
    I was trying to avoid that visual studio creates the obj / bin folders when building the project. is there any way to accomplish this?