What I currently do: When I start up a new project in VS 2012 and pick MVC 4 Internet Application. The first thing I do is go to the Nuget Package Manager and click the "Update All" button.
My question is: Is there a way to take this newly updated project and make THIS a template or is there a place to get updated project templates?
Why I am asking: I want to do this the right way.
Not sure if this is a duplicate: Update default nuget packages
I blogged about how to update NuGet packages consumed by project templates over here: http://www.xavierdecoster.com/update-project-template-to-latest-nuget-packages
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).
i got this problem when i try to install this package Microsoft Azure NotificationHubs in visual studio 2015 enterprise.
image 1
image 2
Could you tell me how you install the package? Do you install as the similar steps below?
In Visual Studio, add a new Visual C# Windows Classic Desktop project to the current solution using the Console Application project template. Name the project ConsoleNotificationhubs.
In Solution Explorer, right-click the ConsoleNotificationhubs project, and then click Manage NuGet Packages.
In the NuGet Package Manager window, search for Microsoft.Azure.NotificationHubs, click Install, and accept the terms of use.
Please note that this package requires .Net Framework 4.5 Full Profile.
If you install successfully, you will get the information like this:
It looks like you are trying to install the Azure Notification Hubs package in a UAP app. You don't need to do it.
Just configure the notification channel per the doc referenced in the comments (cc: Brendan Green).
I have a team working on a client-side node.js application. The sources are stored in a source control. I'd like to modify and debug this application in Visual Studio 2015. They use other IDEs, and I would not like to add additional VS-specific files such as .sln to source control.
I'm able to clone the repository, create a separate empty solution and add the repository as an "Existing Web Site". However, Visual Studio do not recognize package.json, and do not install dependencies as it would for MVC6 projects. Consequently gruntfile.js would not work either.
Is there any way to make Visual Studio see and process package.json, or I'm on a wrong track here?
Instead of using the "Existing Web Site" option, create a new solution and add items to it. Web Site Projects types are a different, legacy project type.
I'm trying to move a solution I have over to Visual Studio 2012 and one of the project types is .vdproj.
According to this link this project type is not supported in Visual Studio 2012:
MSDN says they recommend that you use InstallShield Limited Edition for Visual Studio.
The problem is, when I open up my solution in VS2012 and try to add a new "Enable InstallShield Limited Edition" project to my solution, I get an error message saying:
Creating project 'test'...project creation failed.
Why might I not be able to add a project of this type to my solution?
If I make a new empty solution I can't make an InstallShield project it in either.
I'm going to try to download InstallShield limited edition and see if it does anything.
I tried out that InstallShield download, and it added two extra project types, but I'm unable to create either of them. I'm able to add normal website projects to my solutions just fine, but not deployment projects.
The installer was named the same, but this one prompted me to re-start. After re-starting I was able to add an InstallShield project, but it gets created in its own solution. So, it looks like now I have to figure out how to use it, and I'll be good to go.
It's looking like the limited edition doesn't have support to install Windows services.
This will probably be long and boring because there's lots of steps, but I'd like to write up how to move from a Windows service installer .vdproj to the new InstallShield LE that's available in Visual Studio 2012.
Step 1: Create a merge module (.msm)
Follow the steps of this guide.
Notes:
You will need to install WiX 3.6 and isWiX
The latest release of IsWiX doesn't enable the Tools menu item in Visual Studio 2012. Edit the file: C:\ProgramData\Microsoft\MSEnvShared\AddIns\IsWiXAddin.Addin (XML) and clone the HostApplication element and update 10.0 to 11.0.
In step #8 of the guide, it references a code tab. This has been moved to the XML Editor item in the bottom of the left menu
I left the MergeRedirectFolder empty for my installation
Here is my isWix files view:
After you're done with the guide you should have an empty .wxs file that looks something like this:
Using the Component XML element pulled from here you should end up with a .wxs file that looks like this:
Hit build and you should now have a .msm file.
Step 2: Adding merge module to InstallShield
Go though the wizard to setup the basic install information like company and version information.
Find the redistributables view in ISLE. Right click the list and select browse for module. After your module is found and added, right click the modules and select properties. Set the destination folder drop down to INSTALLDIR. I had to set mine to the lowest level folder I created for my install path, so you might have to experiment a bit.
Build Project, and test on virtual machine
Redistributables Screen
If you're getting errors about the path being too long you might need to change the release location to something close to the root.
Here's a list of all the build errors for reference.
Now you should be able to run your installer and have it install/start a Windows service. A lot more work than .MSI files, we got it to generate in Visual Studio 2010, but overall it was not too bad.
While there is no easy or truly supported solution for Visual Studio 2012, Visual Studio 2013 users can get an extension from Microsoft in the Visual Studio Gallery.
I found this post which says you must download InstallShield first. It's a very confusing way to work. I suggest to vote up the post on the connect site and give them comments letting know how poor that is. They could at least give a more descriptive error http://connect.microsoft.com/VisualStudio/feedback/details/732196/project-creation-failed-for-installshield-limited-edition#tabs
In Visual Studio 2010 SP1, there is an option on the right-click menu on a web project to Add Deployable Assemblies. Phil Haack blogged about it here.
In Visual Studio 11 beta and Visual Studio 2012, this option appears to be missing. Thankfully, you can easily round trip solutions between VS 2010 and VS 11 so I could just open the solution in VS 2010 to add the MVC assemblies to the _bin_deployableAssemblies folder.
Is it just my installation thats broken or do I need to install anything else to get this working?
The Add Deployable Assemblies dialog was a feature that enabled you to deploy MVC or Web Pages projects. It was necessary because in older versions all the assemblies were installed into the GAC on your dev machine but you wouldn't necessarily know if that was the case on the server. Thus this tooling gesture that made your project bin-deployable.
Starting with MVC 3 Tools Update we are now using Nuget package references, which means that your project is automatically bin-deployable. Since the tooling gesture is no longer necessary it was removed from VS 11.