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
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:::::::::::::::
[Update]
I understand I can use 2015 side by side with VS 2010, but we've had problems just polluting our environment. If there is a chance someone has done this, it could save me a lot of time and energy instead of going with an install only to find out it doesn't work. It's also unfortunate this isn't documented anywhere.
So just like the title says.
To give some more background we're hoping to use VS2015 with our testers to kick start using selenium, but our task/bug management is all on TFS2010.
I don't want to distort the testers' environment, neither can I play with any of our dev machines to try this out physically. A VM will just not really run on our, not so fast machines.
My google-fu didn't get me to far. The VS2015 Express features does mention TFS, but I want to know specifically if it supports TFS 2010. Additionally I found a MSDN page. This talks about the various VS and TFS versions but nothing here about VS Express
Related SO posts I found:
Visual Studio 2015 & TFS 2010 Not specific about VS express or not, no definitive answer
Visual Studio 2015 with TFS 2010 More unrelated, this is about builds going wrong
You should be able to run VS2010 and VS2015 side-by-side, but not on the same solution/project files.
Once you open an older project in 2015, a project conversion will happen. If I recall correctly, project compatibiliy started to stabilizer around VS2012, but don't quote me on that, I'd say it is not likely.
You will NOT be able to open the same project in both at the same time afaik, so it's a one-time shift that'd meet your needs.
As far as task tracking systems go, you could also opt in on VSTS and do a one-time export of your existing bugs/tasks. Shouldn't take you more than a day or so to plan and migrate those over.
You can open the project with VS2015 but it will be upgraded to a newer state. We recently done this and could not go back using VS2010. Otherwise you can version control and keep both projects, i.e. the old implementation and the upgraded one. You could try with VS2015 Community Edition.
You sure can run both versions side by side, but not on the same project. Also, the Microsoft Test Manager that comes with Visal Studio 2015 will not connect to TFS 2010. It tells you that it needs an older version of MTM. I am still working out the kinks on our systems.
I am having difficulty in installing Visual Studio 2015 Enterprise (Update 1). After installation completes, I get a warning saying "Not all features installed correctly". See below snip for details
In control panel programs list I found that VC++ 14.0.23506 (both x64 and x86) are installed.
I am able to open visual studio, but when I try to create a new project I get following error regrading c# compiler error
I know performing a clean install again is a solution, but I have poor internet speed and would like to avoid downloading the whole thing again. Any help in fixing this would be great.
PS: I have VS 2013 professional and VS 2012 express also installed, both of which are working fine
Try uninstalling Visual Studio 2015, those VC++ 2015 x86 and x64 runtimes, and reinstalling Visual Studio 2015. Looks like it didn't finish installing properly because you already had the runtimes installed.
My organization upgraded from Visual Studio 2013 to Visual Studio 2015 RC a couple months ago, and we only just now attempted to update some of our existing "db-first" EntityFramework models from our MySQL database. When doing so, we received the following error.
An exception of type 'System.ArgumentException' occurred while attempting to update from the database. The exception message is: 'Unable to convert runtime connection string to its design-time equivalent. The libraries required to enable Visual Studio to communicate with the database for design purposes (DDEX provider) are not installed for provider 'MySql.Data.MySqlClient'.
A quick SO search for this error produced this result from November of 2013 (specifically in reference to VS 2013)...
Apparently MySql and Visual Studio 2013 don't work together yet.
Here is a link on the MySql forums: http://forums.mysql.com/read.php?174,594798,600466#msg-600466
You'll probably need to wait for the next release of the MySql connector.
Does that mean this is likely a comparable issue, and we just have to wait it out until a new MySql.Data client is available that is compatible with VS 2015? Or is it possible that some other cause is to blame (perhaps a bug in VS 2015 RC)?
We're on the latest stable versions of Entity Framework (6.1.3), MySql.Data (6.9.6) and MySql.Data.Entity (6.9.6).
Especially curious to hear if anyone else has stumbled across this issue with VS 2015 RC in particular.
What worked for me was to update the visual studio plugin, available here:
http://dev.mysql.com/downloads/windows/visualstudio/
Could you please update your VS 2015 from RC to RTM, update the nuget packages by running the following command:
update-package
This will get all latest stable nuget package in VS 2015.
Let me know if this fix your issue.
In my case, I installed Visual Studio right after Mysql installing. Therefore Mysql Visual Studio components weren't installed.
To fix that just open MySQL for VS install and pick "Change"
Then check components for target Visual Stadio version
My reputation isn't high enough to leave a comment but this could help someone that ends up on this page. My case was similar to neustart47's however I tried to install the components through mysql installer - community, which failed complaining that VS wasn't installed (or something along those lines), which it was. So make sure to use the stand alone installer and not the mysql community installer. Why this even is a problem, I don't know.
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.