UPDATE: We've determined this to be the result of an issue in our CRM2013 environment, although we haven't been able to identify the issue. We installed a new CRM2013 instance, migrated our organization and solutions, and everything works as expected in the new CRM2013 environment.
ORIGINAL POST: I'm unable to connect to an on-premises instance of Microsoft Dynamics CRM 2013 using CRM Explorer in Visual Studio Pro 2012. When Connect to Dynamics CRM Server is selected from the Tools menu the connect dialog presents and operates normally until the Organization is selected, at which point the dialog closes before a Solution is selected and without selecting Ok or Cancel. No error message is presented.
I've tried starting VS with the /log switch but there are no error messages in the logfile.
I've successfully connected to a CRM 2011 on-premises instance, so the VS Studio install appears to be correct.
At this point I'm wondering if there's a bug in CRM 2013 or an issue with this particular install.
The Dynamics SDK is version 6.10, May 2014.
Visual Studio 2012 Version 11.0.061030.00 Update 4
Crm 2013 Service Pack 1 (SP1) (6.1.0.581) (DB 6.1.0.581)
Related
I created a Custom Checkin policy and build it in Visual Studio 2013 and also build it in Visual Studio 2012 so that whoever using Vs 2012 can use the policy and successfully registered the policy to all machines. I applied the policy to a Team Project from my computer which has VS 2013. In our company some people still use VS 2012. Now whoever is using VS 2012 having issue on checkin. They get this error: Internal error in [Policy Name] policy. Error loading the [Policy Name] policy. Installation instructions: PLease see the web based installation instructions.
So does everybody in our company needs to upgrade to VS 2013?
Thanks for the help!
You should be able to remove the 2013 created policy and add it with 2012. It should then upscale to 2013.
Its the backward compat that's an issue...
The people with VS2012 should un-install 2013 version policy and install a policy with references to TFS2012 dlls.
I'm getting this Message when trying to create a new project:
TFS 2012 Express and Visual Studio 2012 is installed in a separate Machines. All machines are members of the Active Directory, behind proxy and comes with Kaspersky EndPoint 10 MR.
Also I'm a TFS Console Administrator and have the highest rights available.
Visual Studio 2012 Machine Setup:
Professional Version with Update 4;
Windows 7 Pro SP1;
TFS Machine Setup:
TFS 2013 Express (TFS 12.0.21005.1 Tfs2013.RTM);
Windows 7 Pro SP1
Sounds like you need an updated version of Team Explorer (the connector between VS and TFS) since you are using TFS 2013 and VS 2012. VS 2012 ships with Team Explorer 2012 which can connect to TFS 2012 and earlier versions.
Take a look at the compatibility charts: http://msdn.microsoft.com/en-us/library/dd997788.aspx
Perhaps you need Team Explorer Everywhere (TEE): http://www.microsoft.com/en-us/download/details.aspx?id=30661
I figured out that the reason this throws the error message because the Team Explorer and TFS should be aligned with same version. In my context, I was using Team Explorer 2012 which ships with VS 2012 against a TFS Express 2013.
Team Explorer Version and the TFS Version should be the same to avoid this error appearing.
There were few things you could do,
As #madannes mentioned in his post above to use Team Explorer Everywhere
and
As Vivek Bansod explains in the MSDN Forum, I used the Team Explorer for Visual Studio 2013 (The shell version of VS 2013), to create a Team Project and then continued to Add Solution, Check-In and Check-Out operation against TFS Express 2013.
Download Team Explorer for Visual Studio 2013 from this link and create a project there. These projects can be connected to from VS 2012.
I have installed CRM Developer Toolkit plugin for Visual Studio 2012.
I connected to an organization created at DEV server via CRM Explorer in Visual Studio 2012. Entities, Web Resources, and other artifacts are shown in this explorer.
I want to disconnect this CRM Explorer now.
Though I can connect to another Server via Tools-->Connect to Dynamics CRM 2011 Server, but I cant remove it and want to keep it blank, ensuring accidental deployment doesn't happen.
Please let me know in case there is some way to do so.
When I open the "Tools > Connect to Dynamics CRM Server..." menu option, clear any of the fields (usually I just swap http and https radio selections to auto clear), and try to connect, I lose my old connection.
The next time I open VS, it prompts me for the server connection details, though it is not necessary to restart VS in my experience.
This solution works for me
-Tools > Connect to Dynamics CRM Server..." . Then you can log again to your dynamics crm server
Restarting Visual Studio 2012 should disconnect any connected Organization in CRM Explorer. I just tried it on my dev machine and it when I opened the project again it gave me an error saying "No Organization has been specified".
So just save the solution and restart Visual Studio 2012.
Hope this helps.
I want to use SSIS /BIDS project in Visual Studio 2012.
I have both Visual Studio 2010 and Visual Studio 2012 installed along with Microsoft SQL
Server 2012.
VS 2010 was installed first followed by MS SQL 2012 which got me BIDS integrated with VS 2010.
However I cannot seem to find any help on integrating BIDS with VS 2012.
I came across few question on SO related to this topic but all of them had integration with 2010 and not 2012.
I know that with MS SQL 2012 I get a SQL Server Data Tool. Does this mean that Visual Studio 2012 and BIDS cannot be integrated ?
Solution 2012:
I had to update the solution here since one of the answers I received partially solved the issue. The Answer provided by did solve the issue #user2141936 but I kept on getting an BlockMixedArchitectureInstall error while updating an existing instance.
It worked without with creating a new instance!!
Side Note :
Installing the update broken my publishing database project onto 2012 server. You need to download and install a DACFramework patch for it.
Solution 2013:
download and install http://www.microsoft.com/en-us/download/details.aspx?id=42313
Welcome to Microsoft Marketing Speak hell. With the 2012 release of SQL Server, the BIDS, Business Intelligence Designer Studio, plugin for Visual Studio was renamed to SSDT, SQL Server Data Tools. SSDT is available for 2010 and 2012. The problem is, there are two different products called SSDT.
There is SSDT which replaces the database designer thing which was called Data Dude in VS 2008 and in 2010 became database projects. That a free install and if you snag the web installer, that's what you get when you install SSDT. It puts the correct project templates and such into Visual Studio.
There's also the SSDT which is the "BIDS" replacement for developing SSIS, SSRS and SSAS stuff. As of March 2013, it is now available for the 2012 release of Visual Studio. The download is labeled SSDTBI_VS2012_X86.msi Perhaps that's a signal on how the product is going to be referred to in marketing materials. Download links are
Microsoft SQL Server Data Tools Business Intelligence for Visual Studio 2012 (SSIS packages target SQL Server 2012)
Microsoft SQL Server Data Tools Business Intelligence for Visual Studio 2013 (SSIS packages target SQL Server 2014)
None the less, we have Business Intelligence projects available to us in Visual Studio 2012. And the people did rejoice and did feast upon the lambs and toads and tree-sloths and fruit-bats and orangutans and breakfast cereals
Today March 6, 2013, Microsoft released SQL Server Data Tools – Business Intelligence for Visual Studio 2012 (SSDT BI) templates. With SSDT BI for Visual Studio 2012 you can develop and deploy SQL Server Business intelligence projects. Projects created in Visual Studio 2010 can be opened in Visual Studio 2012 and the other way around without upgrading or downgrading – it just works.
The download/install is named to ensure you get the SSDT templates that contain the Business Intelligence projects. The setup for these tools is now available from the web and can be downloaded in multiple languages right here: http://www.microsoft.com/download/details.aspx?id=36843
First Off, I object to this other question regarding Visual Studio 2015 as a duplicate question. How do I open SSRS (.rptproj) and SSIS (.dtproj) files in Visual Studio 2015? [duplicate]
Basically this question has the title ...Visual Studio 2012 / 2013 What about ALL the improvements and changes to VS 2015 ??? SSDT has been updated and changed. The entire way of doing various additions and updates is different.
So having vented / rant - I did open a VS 2015 update 2 instance and proceeded to open an existing solution that include a .rptproj project. Now this computer does not yet have sql server installed on it yet.
Solution for ME : Tools --> Extension and Updates --> Updates --> sql server tooling updates
Click on Update button and wait a long time and SSDT then installs and close visual studio 2015 and re-open and it works for me.
In case it is NOT found in VS 2015 for some reason : scroll to the bottom, pick your language iso https://msdn.microsoft.com/en-us/mt186501.aspx?f=255&MSPPError=-2147217396
I am setting up a VM with a brand new install of TFS 2012 using the RC just released. This is the first time we have tried to use TFS in my company and I need to upgrade some SourceSafe databases. I've also installed the RC for Visual Studio 2012 Ultimate Edition (everything but the MFC foundation classes) but I still can't find the VSSConverter.exe tool.
According to Google it's supposed to be in the Common7\Ide folder, but is nowhere to be seen. Admittedly the only internet links I can find at the moment are for VS2010 so they may be out of date, but I have scanned the entire C drive and still can't find VSSConverter.exe
ps. I know there is a "download and install VSS converter" link in the TFS Admin Console but that just takes me to the Microsoft home page! : http://www.microsoft.com/en-us/default.aspx
VSSConverter is moving away from being a standalone tool and - as you noted - moving to be a part of the TFS Admin Console.
Unfortunately, the VSS -> TFS conversion experience did not ship as part of the TFS 2012 RC. It will instead be included in the released TFS 2012.
In the meantime, the VSSConverter that was included as part of TFS 2010 will properly migrate to a TFS 2012 instance. You will, however, need to install a 2010 instance just to run the tool.
If you do not require the full history, you could simply check-out your VSS databases and then check them into TFS. Another alternative is to install TFS 2010 and use VSSConverter to that database, then perform an in-place upgrade to TFS 2012.