nuget Issue Tracker Rss Feed

Edited Unassigned: upgrade to 50306 razor package will install old version of 20710 razor to the project [3367]

lanlanlee — Fri, 24 May 2013 20:32:36 GMT

Commented Unassigned: Use Nuget to upgrade razor package but actual dll did not get updated (still use the one from cache) [3367]

lanlanlee — Fri, 24 May 2013 20:11:29 GMT

Commented Unassigned: Use Nuget to upgrade razor package but actual dll did not get updated (still use the one from cache) [3367]

lanlanlee — Fri, 24 May 2013 19:56:10 GMT

This issue is found during our servicing release testing for Razor package Microsoft.AspNet.Razor.2.0.30506.0

repro:

1. on a machine only have system.web.razor.dll 20710 version ever installed. (e.g. a Dev11 RTM machine)

2. nuget.exe install packages.config -source "\\aspnet-host\Pub\WSR-NuGet-Candidates\4.0.30506.0" -o "C:\temp\nuget\packages"

3. after executing this command, check the package under C:\temp\nuget\packages you will see the wrong dll (version 20710), instead of the one come with new package version 20715.

Comments: Add more investigation information. Here are something very strange. If we install from online official location (20715.0) package, it will install the 20715 version of dll. If we install from Ron’s private patch location (\\aspnet-host\Pub\WSR-NuGet-Candidates\4.0.30506.0 ), it will install 20710 version of dll. Although from all aspects, Ron’s package should carry the 20715 dll (we used package explorer and save dll locally to verify). Is there anything else need to be included in the package to specify override local cache? Or is there any difference on behavior regarding if the packages are from official path or private path?

Edited Issue: VS2012 hangs in NuGet package manager [3093]

murilorocha — Fri, 24 May 2013 19:10:00 GMT

Commented Issue: VS2012 hangs in NuGet package manager [3093]

murilorocha — Fri, 24 May 2013 19:09:35 GMT

I am experiencing a hang in Visual Studio 2012 using NuGet package UI.

Its a fairly big (66 projects, 4 pages of NuGet packages) solution, closed-source commercial.

Flow:
1. Right click solution node in Solution Explorer
2. Manage NuGet packages for solution...
3. Select any package in installed packages
4. Visual Studio starts to load projects again (1 in 18)
5. It hangs forever.

Repeatable until I delete my solutions .suo, after which it magically works.
After a few days, the issue reappears.

I understand that this is not alot to go on, but I would like to help anyone interested in debugging this issue.

I am using:
- Visual Studio Premium 2012 Update 2 CTP
- ReSharper 7.1.1 C# edition
- NuGet package manager 2.2.40116.9051
Comments: The hang described by @thomaschrstnsn is a duplicate https://nuget.codeplex.com/workitem/2864. @thomaschrstnsn Thanks for reporting! @bbobkins Your hang seem to be different from the one in the description. Could you please create another bug? Try to add more information as @dotnetjunky said - Do you have one solution and two projects inside of this solution? - What is the exact moment the hang starts? When you click on "Update" beside the package description?) - What is your NuGet version? (Help > About Microsoft Visual Studio)

Created Unassigned: Use Nuget to upgrade razor package but actual dll did not get updated (still use the one from cache) [3367]

lanlanlee — Fri, 24 May 2013 19:08:42 GMT

Commented Issue: Multiple versions of a package installed in solution when managing packages at project-level [3123]

mbenford — Fri, 24 May 2013 05:40:18 GMT

I recently noticed an issue with the way the "Manage Nuget Packages" feature works at the projetct level.

Here's a scenario that happened yesterday:
* A team member wants to add a reference to package A in one of the solution's project
* He opens the "Manage Nuget Packages" dialog at the project-level
* He searches for "Package A"
* He selects the Package A version 1.1 from the result list and clicks on the Install button
* This project now refers to Package A v1.1 while all other projects refer to v1.0
* The solution stops compiling because of version mismatch

Never during the process the user is notified that another version of the same package is installed elsewhere in the solution. Neither he's proposed to update the installed package to this new version.

I propose the following ideas as ways to prevent that issue and make the whole process smoother:
* Prevent the user to manage package at the project level (this option could be set at the solution level so each team can choose if they allow it or not).
* Notify (warn) the user that another version of the same package is already installed in the solution and allow him to use the installed version, update the installed version to the newer version or let him install the selected version for the current project only (hope he knows what he's doing).
* Show the solution's installed packages in each project dialog but gray them if they are not install in the current project. Another option could be to show the green checkmark icon next each package installed in the current project (similar to the search result list behavior).

Comments: I had some problems related to that situation, and wrote a little tool to check if there are different versions of a same package in use across a solution. Perhaps it could help others prevent some problems that may arise in such cases until a definitive solution comes out. It can be found at http://github.com/mbenford/nucheck.

Commented Unassigned: Opening http proxy for nuget traffic to nuget.org also requires domain az320820.vo.msecnd.net to be opened [3364]

8DH — Thu, 23 May 2013 19:18:21 GMT

Hi!

We have our build park installed on our internal servers and they have no internet access by default. In order to give them access we need specific exceptions enforced in our http proxy. Today I and a colleague did this and my colleague discovered that apart from nuget.org we also had to add an exception for the host az320820.vo.msecnd.net. Without the exception nuget install etc just wont work.

While this current setup works, the name suggests that it could be changed at any time which will break our proxy setup.

Would it be possible to remove the client access to az320820.vo.msecnd.net or can it be assumed that you never will move away from that resource?

Regards, Daniel
Comments: Ah, I see. Can one expect that address to remain stable over time? Regards, Daniel

Closed Unassigned: Opening http proxy for nuget traffic to nuget.org also requires domain az320820.vo.msecnd.net to be opened [3364]

dotnetjunky — Thu, 23 May 2013 17:40:18 GMT

Hi!

We have our build park installed on our internal servers and they have no internet access by default. In order to give them access we need specific exceptions enforced in our http proxy. Today I and a colleague did this and my colleague discovered that apart from nuget.org we also had to add an exception for the host az320820.vo.msecnd.net. Without the exception nuget install etc just wont work.

While this current setup works, the name suggests that it could be changed at any time which will break our proxy setup.

Would it be possible to remove the client access to az320820.vo.msecnd.net or can it be assumed that you never will move away from that resource?

Regards, Daniel
Comments: This is by design. We distribute package binaries through the CDN network. You need to allow access to that host.

Closed Unassigned: can you make me the package owner of should on nuget.org [3366]

dotnetjunky — Thu, 23 May 2013 17:35:36 GMT

Commented Unassigned: can you make me the package owner of should on nuget.org [3366]

dotnetjunky — Thu, 23 May 2013 17:35:30 GMT

I need to update my package and it looks like it is an orphan on nuget.org.

https://nuget.org/packages/Should/

I am the owner of this library, my nuget account is erichexter

Here is where I maintain the project source. https://github.com/erichexter/should

Comments: Can you following the instruction on this page to file a request to the team? http://nuget.org/policies/Contact

Commented Issue: "Nuget pack" ignores dependencies from packages.config [3097]

NoLoComprendo — Thu, 23 May 2013 13:39:01 GMT

Assumption:

* There is a Visual Studio project (.csproj) without related solution (.sln) yet

If there isn't a packages folder in the "top-level" folder of the .csproj file folder, "Nuget pack" does not recognize the dependencies defined in the package.config next to a .csproj file.

To overcome this issue, you can place an empty solution (.sln) and a nuget.config (containing the path of the packages folder) on the top-level folder of the .csproj folder.

__Example:__

Assume you have the folder structure:

* MyProjects\MyProject\MyProject.csproj
* MyProjects\MyProject\packages.config

In order to make "nuget pack" recognize the dependencies defined in packages.config you have to place the following files in the MyProjects folder, otherwise it won't work:

* MyProjects\MyEmpty.sln
* MyProjects\nuget.config (containing path of packages folder)

So, the question is why is there this empty .sln or even the nuget.config with the path to the packages folder necessary? The packages.config next to the .csproj file should be totally sufficient for "nuget pack" to add the dependencies.
Comments: I've come across this issue (using nuget 2.5), but have a slightly simpler workaround My solution layout looks like the below: root/ - lib/ - NugetPackage1/ - ... - src/ - .nuget/ - nuget.config - nuget.exe - nuget.targets - MyProj/ - MyProj.csproj - packages.config - MySln.sln (Where the nuget.config is the one attached.) To workaround the error, one can copy the nuget.config into the "MyProj" directory. Everything then works as it should, although I've not tested it using the recursive "-IncludeReferencedProjects" feature of 2.5.

Created Unassigned: can you make me the package owner of should on nuget.org [3366]

erichexter — Thu, 23 May 2013 13:06:54 GMT

Commented Feature: Allow package resource folders to be configurable [1914]

koistya — Wed, 22 May 2013 23:53:39 GMT

I <3 Nuget. But one thing I don't like is that it forces things like JavaScripts to be in one location. I keep my website organized a specific way, and I don't want my scripts in that folder. So it would be nice if certain folders could be configurable to drop items in an alternate location.
Comments: How about this: ![Image](http://i.imgur.com/4f308dT.png) We don't even need an interface for this for the first time.

Edited Unassigned: NuGet adds reference to older version rather than reuse existing one [3365]

Sinus — Wed, 22 May 2013 16:31:25 GMT

In my solution 8 projects have references to NHibernate 3.3.3.4000 package. Because it requires Iesi.Collections (>= 3.2 && < 4.0) all of them also references to Iesi.Collections 3.3.1.4000

While trying to add reference to NHibernate from 9th project, NuGet 2.5.40416.9020 downloads Iesi.Collections 3.2.0.4000 and adds reference to it (rather than reuse existing Iesi.Collections 3.3.1.4000)

Steps to reproduce:
1. Create solution with 2 project (Project1 and Project2)
2. Execute in Package Manager Console: install-package Iesi.collections -version 3.3.1.4000 -ProjectName Project1
3. Open “Manage NuGet Packages for Solution...” window and install latest NHibernate (3.3.3.4000) for both projects
Result: Project2 references to Iesi.Collections 3.2.0.4000 and there are two versions of Iesi.Collections in 'packages' subfolder of the solution
Expected: Project2 references to the same Iesi.Collections 3.3.1.4000 as Project1

Created Unassigned: NuGet adds reference to older version rather than reuse existing one [3365]

Sinus — Wed, 22 May 2013 15:59:44 GMT

Created Unassigned: Opening http proxy for nuget traffic to nuget.org also requires domain az320820.vo.msecnd.net to be opened [3364]

8DH — Wed, 22 May 2013 15:30:07 GMT

Created Unassigned: Ability to Specify Location of the NuGet Cache Directory [3363]

jed624 — Wed, 22 May 2013 12:12:59 GMT

I use NuGet to share the output of CI builds with other software components. I've wired up a system that uses the command line .exe to pack, push, and install dependent modules, and I frequently run into this error running the install command in builds that share a common component:

GET <URLToMyFeed>/Packages()?$filter=tolower(Id) eq '<MyPackage>'&$orderby=Id
System.IO.IOException: The process cannot access the file 'C:\Users\<buildUser>\AppData\Local\NuGet\Cache\<MyPackage>' because it is being used by another process.

followed by a stack trace.

This error is caused by concurrent builds on the same machine, both of which require <MyPackage> to build, executing the install step, unpacking the software to their workspace, but then simultaneously sticking a copy of the package in the cache directory, which is a common location. Additionally, the packages are kind of large, so it increases the odds of collision.

As far as I can tell, I cannot control the location of the cache directory, either as an option via the install command, or in the NuGet .config file, to help eliminate this contention point. The only way I think I can solve this class of problems, is to ensure the builds do not run concurrently, or separate them to different systems. I have a number of different modules, though, and I'd like to better utilize my system resources.

It would be great if there was the ability to provide some option(s) on the command line during install to specify a cache directory which would allow each build to have it's own cache location, and/or the ability to not post a copy of the package to the cache.

Thanks

Commented Unassigned: Issue while using NuGet Transform in Config [3360]

rishig — Wed, 22 May 2013 07:56:39 GMT

I have two packages for my solution where Package 2 is dependent on Package 1. Package 1 contains the configuration file & it is updated with a tag when Package 2 is installed. Now, when I remove package 2 keeping Package 1 intact, it strangely removes one Attribute from one particular tag. Please help me solve this issue.

Following are the screenshots:

Below screenshot shows configuration file after installing Package 1 & 2:

![Image](http://i1329.photobucket.com/albums/w552/rishigohil10/Config_After_Installing_Package_2_zps674f4f3c.png)

Below screenshot shows configuration file after removing Package 2 and keeping Package 1:

![Image](http://i1329.photobucket.com/albums/w552/rishigohil10/Config_After_Removing_Package_2_zps9883b1d9.png)

Comments: Also, I found another issue after adding the tag. The newly added tag is not in correct format. Please help how can I format my desired tag.

Commented Unassigned: Issue while using NuGet Transform in Config [3360]

rishig — Wed, 22 May 2013 07:55:08 GMT

I have two packages for my solution where Package 2 is dependent on Package 1. Package 1 contains the configuration file & it is updated with a tag when Package 2 is installed. Now, when I remove package 2 keeping Package 1 intact, it strangely removes one Attribute from one particular tag. Please help me solve this issue.

Following are the screenshots:

Below screenshot shows configuration file after installing Package 1 & 2:

![Image](http://i1329.photobucket.com/albums/w552/rishigohil10/Config_After_Installing_Package_2_zps674f4f3c.png)

Below screenshot shows configuration file after removing Package 2 and keeping Package 1:

![Image](http://i1329.photobucket.com/albums/w552/rishigohil10/Config_After_Removing_Package_2_zps9883b1d9.png)

Comments: [Framework](http://d.pr/f/5nes) - Package 1 [Log](http://d.pr/f/58Hk) - Package 2