I'm at a loss.
I've installed a fresh instance of SQL Server Express 2012, loaded a fresh install of TFS2012. I attempted to hook my copy of VS2010 and I can't create a new project.
I started here and installed the service packs, the updates and the compatibility packages. I made myself an admin (of everything) from the TFS2012 console. When I go to to create a new project from the Team Explorer I get the TF30172 error.
My permission window
I'm flummoxed. I just ran this again. Anyone have any suggestions?
As far as I know Visual Studio 2010 can connect to TFS 2012 for development activities, but cannot directly create team projects for 2012. In fact, many administrative tasks (create Team Projects, build definitions, etc) in 2012 don't work from a 2010-based Team Explorer.
The solution is to upgrade to VS2012 or later, or to install Team Explorer 2012 to create team projects while continuing to use VS2010 for development.
Sadly Microsoft doesn't really declare this anywhere so it can be hard to find the answer.
See also: Can't create Team project in tfs 2012 using visual studio 2010
Visual Studio 2010 can't work on TFS 2012. Installing the latest VS.NET should solve this. Generally, the rule of thumb is, new versions are backwards compatible. So VS.NET 2010 can connect to 2010/2008/2005 etc. VS.NET 2012/13 can connect to 2013/2012/2010/2008/2005. But connecting from 2010 to 2012 won't work.
Related
I am attempting to run a simple SSIS package in Visual Studio (15.9.0). This is the first time I've used SSIS. My error message is at the bottom, because it's quite lengthy. Directly below is my attempt to fix the error.
I followed the directions of this link:
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017
1.) I selected the checkboxes for "Data Storage and Processing" in Visual Studio Installer
2.) I uninstalled SSDT
3.) I downloaded SSDT for Visual Studio (15.8.2)
4.) I selected the "SSIS" checkbox on the installation of SSDT.
I am continuing to get the error message below. Thanks for any help in advance!
>
Failed to start project (Microsoft Visual Studio)
===================================
The directory name is invalid
(Microsoft.DataTransformationServices.VsIntegration)
------------------------------ Program Location:
at
Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.LaunchVsDebugger(IVsDebugger
iVsDebugger, DataTransformationsProjectConfigurationOptions options)
at
Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.ValidateAndRunDebugger(Int32
flags, IOutputWindow outputWindow,
DataTransformationsProjectConfigurationOptions options) at
Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32
launchOptions, ProjectItem startupProjItem,
DataTransformationsProjectConfigurationOptions options) at
Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchActivePackage(Int32
launchOptions) at
Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32
launchOptions, DataTransformationsProjectConfigurationOptions options)
at
Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.Launch(Int32
launchOptions, DataTransformationsProjectConfigurationOptions options)
>
Answer 2
See the response from Microsoft.
https://social.msdn.microsoft.com/Forums/Windowsserver/en-US/aa3a46fb-2f09-4808-b6db-baa1553f6401/failed-to-start-project-microsoft-visual-studio?forum=sqlintegrationservices
Answer 1
Based on the question and user comments, I think you may have installed SSDT incorrectly. When installing SSDT, you need to select Install SSDT for 2017 with a new instance of VS 2017. Then, Select Integration services (kind of mandatory here b/c thats what you are installing), Reporting Services and/or Analysis Services.
https://developercommunity.visualstudio.com/comments/345539/view.html
Update 1
SSIS has a long and tortuous history with Visual Studio integration - it used to just install as a new set of Business Intelligence projects (i.e., SSIS, SSRS, and SSAS) within Visual Studio itself, without requiring a new standalone installation (at least up through VS 2013, I never used VS 2015). Even the product's name has gone through a circus show: it went from DTS, to SSDT-BI, to SSDT - stay tuned for more changes from the marketing department folks!
As of VS 2017, SSDT has to be installed as a new instance of Visual Studio. This means that you will effectively have two instances of Visual Studio installed on your machine:
For all SSDT related projects (i.e., Integration Services [IS], Reporting Services [RS], and Analysis Services [AS]).
For all other non-SSDT related projects.
Note: I do not fully understand why Microsoft chose to split the development of SSDT into a standalone instance of VS 2017, but personally (and this is my own 2 cents) I hate it. The new Preview release cadence model has led to more problems than solutions and has made the relationship between VS2017 and VS2017 SSDT so unstable that I only install new preview releases on test boxes before installing them on my own. Microsoft has released some really bone-headed bugs (i.e., unable to deploy package from project, unable to open VSTA for script tasks/components due to regression issue with VS2017). It is enough to drive one bonkers. I currently use the following:
Visual Studio 2017 (SSDT): 15.8.2
Visual Studio 2017: 15.7.6
I finally got my SSIS package to run successfully! I was previously running Windows 7 64 bit OS and the version of SQL Server was 32 bit. I installed Windows 10 64 bit OS and now my SSIS package ran successfully. It seems that the OS and SQL Server must both be 64 bit.
Below are the different versions of technology I'm running
Windows 10 64-bit Operating System
- SQL Server Standard 2012 (64-bit)
- Visual Studio Professional 2017 (Version 15.9.4)
- SQL Server Data Tools for VS 2017 (Version 15.8.2)
- SQL Server Management Studio (Version 17.9.1)
- The Project Template inside of VS was named "Integration Services Project" under the "Business Intelligence" tab.
Links
SSIS Tutorial I was executing: https://www.youtube.com/watch?v=zwUhHIpRoIA
SSDT: https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017
Script editor in VS 2017:::::::::::::::
We're growing the team but won't buy more Visual Studio Ultimate licences, so some people will have to work in VS Express edition.
We're testing it, but our projects aren't working on Express. We have projects of type Class Library - compiles into dll - and Console Application. In VS Express, when I try to create new solution/project, all I have is asp.net web application. I believe the installation I did doesn't have support for these templates, and therefore is unable to load those projects.
Is there a way to fix it? Maybe use another Express setup or install those templates separately?
Visual Studio Community will be work for you. You can download it from here: https://www.visualstudio.com/vs/community/
I installed Visual Studio 2015 Express for Desktop and those project templates became available.
I'm working with Visual Studio 2012 Express (Update 4) with Windows Azure Tools 2.5. I have the Remote Tools installed for Visual Studio 2012 Express Update 4.
I'm running some WorkerRoles on Windows Azure, and I need to do some debugging on the staging version.
My understanding is that I can connect to Azure using the Database Explorer in VS and find the process and attach the debugger to it. I've been following various tutorials around the net that all say the same as this one (which is actually very well written): http://geekswithblogs.net/shaunxu/archive/2013/11/02/remote-debug-windows-azure-cloud-service.aspx
The problem I have is that when I hit publish, and go to advanced settings, there's no option to enable debugging. According to everywhere it should look like this:
But I don't have those options:
Later, when I go to the cloud services in the database explorer, and I right click on the role I want to attach to, there's no option to "Attach Debugger":
Is this a limitation of VS2012 Express?
Any help would be hugely appreciated.
Cheers,
Chris
EDIT:
As in the tutorial I have the Build Configuration set to Debug:
I realise that this may/may not help others experiencing this problem.
I solved the problem by completely uninstalling all the different versions of Visual Studio, .NET, SQL Server tools. I had tried so many different versions of things that Azure tools and things may not have been applying to the correct version.
Here's the important bit:
The version I'm working with now is Visual Studio 2012 Professional.
If re-installing doesn't solve the problem, Visual Studio 2012 Pro has these features.
I already have a project which is ready to build. Currently, I am using visual studio 2013.
But, I don't know how to create an MSI setup in visual studio 2013, but for visual studio 2010 there are plenty of tutorials out there discussing how to create a setup in visual studio 2010.
Does this mean I need to install visual studio 2010 in order to create an application setup for my project?
What is the easiest way to create an application setup in visual studio 2013?
Microsoft has listened to the cry for supporting installers (MSI) in Visual Studio and release the Visual Studio Installer Projects Extension. You can now create installers in VS2013, download the extension here from the visualstudiogallery.
visual-studio-installer-projects-extension
As of Visual Studio 2012, Microsoft no longer provides the built-in deployment package. If you wish to use this package, you will need to use VS2010.
In 2013 you have several options:
InstallShield
WiX
Roll your own
In my projects I create my own installers from scratch, which, since I do not use Windows Installer, have the advantage of being super fast, even on old machines.
Visual Studio 2013 now supports setup projects. Microsoft have shipped a Visual Studio extension to produce setup projects.
Visual Studio Installer Projects Extension
Microsoft recommends to use the "InstallShield Limited Edition for Visual Studio" as replacement for the discontinued "Deployment and Setup Project" - but it is not so nice and nobody else recommends to use it. But for simple setups, and if it is not a problem to relay on commercial third party products, you can use it.
The alternative is to use Windows Installer XML (WiX), but you have to do many things manually that did the Setup-Project by itself.
Microsoft also release the Microsoft Visual Studio 2015 Installer Projects Extension This is the same extension as the 2013 version but for Visual Studio 2015
Apart from Install Shield and WiX, there is Inno Setup. Although I haven't tried it myself I have heard good things about it.
I will tell , how i solved almost similar problem. I developed a application using VS 2013 and tried to create wizard for it failed to do. Later i installed premium VS and tried and failed.
at last i used "ClickOnce" and it worked fine.
So i believe here also , "CLICKONCE" would help you.
After installing TFS 2012 Express Beta x32 problems connecting old remote TFS 2010 server.
When I try to open Source Control for old TFS 2010 server - recieve error:
Team Foundation Error
Method not Found: 'Boolean
Microsoft.TeamFoundation.VersionControl.Client.Workspace.OwnerNameMatches(System.String)'.
Is it possible to fix this problem. Can't access code files. Team system works ok. Documents are available also.
Can you be more clear on exactly what you did and where you did it? For starters, there's no such thing as TFS 2012, but I'm assuming you're talking about the TFS 11 beta.
Did you install TFS11 Express Beta on the same machine where you run Visual Studio 2010? Or did you install the TFS11 Team Client on your Visual Studio 2010 system? Did you also install Visual Studio 11 on that same machine? Are you now getting this error in VS2010?
Without knowing more about your setup, my guess is that you installed a new version of the TFS client tools and now your VS2010 is getting mismatched versions of the assemblies. (In particular, the method it's complaining about does not exist in the 2010 version of the client; I assume its new in v11.)
I had similar problems, though not TFS related, when installing VS11 side-by-side with VS2010; the ultimate fix was to uninstall VS2010 completely, then reinstall and re-service-pack VS2010. I'd also suggest not installing VS11 or TFS11 on a production machine until it's out of beta, unless you're willing to deal with this exact type of problem. (It's called beta for a reason...)
Try the KB2662296 hotfix:
Microsoft Download