I am trying to use Visual Studio 2012 as an IDE for Meteor.
I want to change behaviour of VS2012 for building and publishing. So that there is nothing for VS to build, when I will click build button, I want VS2012 to just run meteor command inside a ruby command window.
And when I will click publish button, I want VS2012 to deploy my application to (appname).meteor.com
For both cases I will need to set paths. I am trying to modify project file but so far no luck...
Any help appriciated.
Related
1) I set my preferences to open up Unity .cs files using Visual Studio 2012
2) I came across this: https://visualstudiogallery.msdn.microsoft.com/7ab11d2a-f413-4ed6-b3de-ff1d05157714
and I download and installed VS2012 Tools for Unity
3) Now I'm stuck here, when I try and run/debug a single .cs file in VS, I get this exception:
"A project with an Output Type of Class Library cannot be started directly. In order to debug this project,add an executable project to this solution which references the library project. Set the executable project as a startup project."
I'm not sure what that means and how to proceed. I'm not sure how to sync up Unity with Visual Studio.
Anyone?
Btw, I have Unity free version 4.6.1 installed and Visual Studio Premium 2012.
Thanks
http://unityvs.com/
Once you have installed the correct version for your VS version you need to open your unity project (in unity) and add the VS tools package ...
Assets > import package > Tools for unity 20xx
Then you need to set your default editor in ...
Edit > Preferences > External Tools
Then when you click on scripts in unity it should open them in VS.
Now from VS you should have the option to attach the unity debugger where it normally says "debug" in the toolbar.
After attaching your debugger to unity run your game by hitting play in unity and it should hit any breakpoints you have set in VS.
All should magically work.
Close visual studio and Unity.
Download and install Tools for unity 2012 and links to other versions can be found here:
https://visualstudiogallery.msdn.microsoft.com/7ab11d2a-f413-4ed6-b3de-ff1d05157714
Open Unity 3d
Then like Wardy said:
Assets > import package, Select "Tools for unity 2012"
Edit > Preferences > External Tools, select 2012
I had the same error massage using unity 2018 & visual Studio 2017. Frankly, closing VS and opening it after double clicking on a unity script (inside unity) solved it.
I can't find any documentation on how to publish your app to the app store from Visual Studio? Is this a case of having to use Xamarin Studio once you are ready to submit your app?
It seems a bit odd that xamarin gives you the opportunity to use Visual Studio but then has absolutely no instructions on how to create a bundle to submit your app to the app store..
Any tips on how to do this with Visual Studio would be great.
As far as I know, there's no way of submitting to AppStore (or even TestFlight) from VS.
I believe that you can only submit builds to the App Store using Xcode or Application Loader. Both Mac programs.
Personally I make a release build in Visual Studio, and then click the 'Show IPA File In Build server' button.
If the buttons greyed out, right-click your iOS solution, select properties. Then go to 'iOS IPA Options' and check 'Build ad-hoc/enterprise package (IPA)'
Then I go to my Mac and start up Application Loader and drag the IPA file there.
We have upgraded our TFS installation from 2012 to 2013. When running our builds they will fail with the following error if unit tests are enabled:
TF900547: The directory containing the assemblies for the Visual Studio Test Runner
is not valid ''
The build process template or build definitions has not been changed after the upgrade. The upgrade process did not change them. Where can I provide the path to the Visual Studio Test Runner and where is it located on disk?
I do not know if "Visual Studio Test Runner" is a new option for 2013 or if this setting was also used before, when we were using TFS 2012.
We use Visual Studio Professional 2012 on the build server.
To do the second choice in Oswald's answer:
Right click on your build definition and select "Edit Build Definition..."
Click on the "Process" group in the build definition.
Find the "Automated Tests" group under "Build Process Parameters" and click on the ellipsis.
A "Automated Tests" dialog box will appear, select the test under "Tests to run" that you want to edit.
Click on the "Edit", a "Add/Edit Test Run" dialog box will appear.
Change the test runner to "MSTest.exe test runner"
Note: I am using TFS2012
You have two choices:
Install Visual Studio 2013 or the Agents for Microsoft Visual Studio 2013 if you want to continue to use the Visual Studio Test Runner.
Switch to MS Test as the test runner and change the Tools Version in the Build-Workflow. This will allow you to continue using Visual Studio 2012 on the build server.
Note: Tank you SteveC to post the link to the agents only site
The solution for us was to install the Agents for Microsoft Visual Studio 2013, rather than Visual Studio 2013
As an alternative to installing Visual Studio on the build machine, you can simply copy the files from your local machine to the build machine.
ZIP the TestWindow folder found in
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft
then copy it to the build machine, and unzip to the same location.
We had the same problem as the OP but, because the TFS server is considered a production box (other departments use it for other things), we were not permitted to install VS2013 on the server. The same applied to any third party tools needed for builds, they were a pain to integrate into the build.
I eventually worked round this by using another dev box to act as a build server for TFS. By installing the Build Server component of TFS on the dev box and setting up a controller and build agents on that box, TFS could pass the responsibility for the actual build to the dev box, on which we could install anything, without compromising the TFS server itself.
While it is not perfect - an extra box and VS2013 license needed - it is by far the easiest way to avoid poluting a production TFS box. Alternatively, nominate a developer's own box and install the build agent there - the environment is ready built, it will simply slow down a little during a build.
If your project does not have unit tests, you can just disable the unit test execution on the build definition.
To do that, edit the build definition, under process tab, delete everything in field "Automated Tests"
I'm using Visual Studio 2012, update 1 on a Windows 8 machine. When I try to start a new win32 project using the application wizard something weird appens:
the windows that welcomes to the wizard has three empty bullets under "these are the current project settings". Both the cancel and the finish button do not work.
The folder for the application is created but no files inside.
please help!!
I solved my problem forcing a "clean" install of VS2012. ('clean' means that also the shared packages were uninstalled). Presuming that the installer I used to install VS2012 was on d:
D:\vs_premium.exe /uninstall /force
Once reinstalled, the problem was gone.
I am running Visual Studio Express 2012 for WP on Macbook via Parallels.
I did the update of VS today and could not load my project (HTML App, #C) nor create new projects afterwards.
The solution was to go to Windows program uninstall for Visual Studio Express 2012, BUT choose option "Repair". It took about the same time as the update but I was able to create new projects afterwards (my existing own app project from November 2012 also works).
Before I "repaired" the installation, I have removed manually from VS->Tools->Extensions and Updates a few packages added "Nu Get Package Manager and Packager". I am not sure if the latter is really needed.
Additional info: My VS 2012 Express for Windows8 installation worked and works w/o issues.
I'm trying to create a site using Orchard CMS. To get started, I downloaded / installed Orchard from WebMatrix. I successfully setup a site using the "Default" recipe. I then click the "Files" tab within the accordian along the left side. From here, I can see all of the files in my project. To begin editing within Visual Studio 2012, I click the "Visual Studio" button in the ribbon.
Once inside Visual Studio, I right-click on the solution and select "Rebuild Solution". The solution begins building, but then I receive an error. The error says:
Error 1 Object reference not set to an instance of an object. C:\Users\username\Documents\My Web Sites\Orchard CMS2\Modules\Contrib.Cache\Contrib.Cache.csproj 1
Please note that at this point, I have not even edited a single file. Rather, I created a basic site and attempted to open it in Visual Studio. What am I doing wrong?
Only the full source code will build in Visual Studio. You can edit the compiled web site version that you downloaded in Visual Studio, but you won't be able to build it. It actually doesn't need building as it has dynamic compilation built-in.
If you want to build the framework and core, get the full source code version.