I have a C# project which has a 2 Project References from projects within my Solution.
It also has 5 NuGet package references from packages in my NuGet repository.
Given the .csproj, How can I generate or create the nuspec file using NuGet Project Explorer tool?
And how to validate if this nuspec is indeed correct?
You can do this using NuGet.exe with the command line similar to:
NuGet.exe spec Project.csproj
To do this from within Visual Studio you could add a new External Tool (from the Tools menu) which uses NuGet.exe.
NuGet Project Explorer supports NuGet packages but not project files so one of the above techniques would be simpler. For the NuGet Project Explorer you would need to write a custom addin.
For validation, NuGet.exe will generate the .nuspec file so it should be valid. Also when you use NuGet.exe pack YourNuspec.nuspec it will be validated when you create a NuGet package with warnings output to the console.
Related
I have created a Xamarin.iOS UI component without core project, only a Xamarin.iOS project, and I would like to package it with nuget which I can use across several projects. But I can't handle it.
I'm looking for proper steps for creating a Nuget Package based on my Xamarin solution.
The only thing I found is this command line nuget pack your.nuspec.
Obviously I'm on mac.
Thank's
Anthony;
Easiest way to make a nuget for ios - Visual studio for Mac.
Open project settings in ios settings page and enable "create package when building the project".
Then go to the Metadata and fill it. After that choose release mode and build, and finally check output directory(yourprojectname/bin/release).
We have a directory in TFS (a team project) where all our internals and third parties DLL are referenced. It's works great, all our project references these directory.
When I configure an automatic build of my project, I would like that TFS automatically download the latest version of this directory, before TFS do my build. I could configure it?
By the way: We use VS2012 and TFS2012.
Thank you.
In a XAML build, map the TFVC folder where those assemblies are stored under the "Source Settings" tab.
I am doing some investigation of NuGet to determine if I can use it to distribute various software components. All of these components are C++ based so I'm using CoApp PowerShell Tools to create the NuGet package files. I have placed these .nupkg files on a network folder for distribution. However, when accessing the packages via Visual Studio 2012, I can only see the latest version. Is there a way to view all of the versions of a particular package?
Here is the network folder:
Here is what I see in Visual Studio 2012:
You're supposed to only see the latest version. If you want to install a specific version, you'll have to use the Package Manager Console.
Install-Package SYS_STANDARDS -Version 1.3.1.0
If that isn't acceptable for your requirements, then Nuget isn't the best way to distribute your code.
Newer versions of Visual Studio have a drop down menu that can be opened to view and select different versions of a package
I woulkd like to create a Visual Studio extension. I chose the Package option since the AddIn option will be deprecated from Visual Studio 2013 and above.
So i installed Visual Studio 2012, and Visual Studio SDK 2012, and created a new VS Package project.
Now, I want my package to enable the user to create a new type of project. i.e: I want to extend the right click->new project options to contain a new model of project, which will be a standard Visual C++ project, with some additional configurations, links, references and etc.
I googled a lot, but found nothing.
Does any of you have an idea about this target?
Thanks in advance!
I think the Visual Studio Template Schema Reference contains all information you need to create custom project templates; see: http://msdn.microsoft.com/en-us/library/xwkxbww4.aspx
You can derive a project template from an existing project, which might be the way to go, since it creates a valid template that only needs some customizing. A template export can be done by using the Export Template command found in the File menu.
The template wizard will create a ZIP file containing the template manifest and all referenced files; just extract the archive and customize it in the way you want it (add/remove files, change information like name and description in the manifest). Once you´ve your customized template, create a new VISX package project and add the template ZIP file to it (using Add Existing Item command).
The last step will be to add an Asset to the VISX manifest. Open the source.extension.vsixmanifest file in the VSIX designer, goto the Assets tab and click the New button; this will open a dialog to setup the asset... choose Microsoft.VisualStudio.ProjectTemplate as the type - and File on filesystem as the source. This will allow you to pick the previously added ZIP file. Build the package - and you´re done.
So I'm using Artifactory to host my NuGet packages and we have 2 different repos for 2 different solutions.
Each solution has a local Nuget.config file that adds its own source right after running the command (which doesn't seem to work in VS) and disables the standard Nuget feed.
The problem is that if I open the Package Manager Settings in visual studio, choose the package sources sub section and click ok, VS will then save that custom repo in the %appdata%/Nuget/Nuget.config file. So now when I open the other solution it will see both repositories.
Thanks for reporting the issue. Ported it over to codeplex as https://nuget.codeplex.com/workitem/3794. Thanks.