I'm going through the Microsoft Multidimensional Modeling (Adventure Works Tutorial) and have come across the following error message when I try to create a new attribute relationship. I have tried uninstalling and reinstalling everything. I'm using the 2022 version of Visual Studio and the 2019 version of SSMS. I am connected through the localhost account (but had to use a specific Windows user name and password as it would not deploy through the service account). Any thoughts?enter image description here
===================================
Service provider has to support IUserPromptServive! (Microsoft Visual Studio)
Program Location:
at Microsoft.AnalysisServices.Design.AR.EditRelationshipsDataProvider.Init(Dimension inDimension, IServiceProvider inServiceProvider)
at Microsoft.AnalysisServices.Design.AR.EditRelationshipsDataProvider..ctor(Dimension inDimension, DimensionAttribute inAttribute, IServiceProvider inServiceProvider)
at Microsoft.AnalysisServices.Design.AR.CommonMenuHandlers.CreateAttributeRelationship(MenuCommand menuCommand, CommandHandlingArgs args)
at Microsoft.DataWarehouse.Design.CommandHandlingInfoMap.HandleCommand(MenuCommand menuCommand)
at Microsoft.AnalysisServices.Design.AR.CommonMenuHandlers.InvokeCommand(MenuCommand menuCommand)
Looking for information about the same problem, I found that this is a bug of VS 2022
https://developercommunity.visualstudio.com/t/service-provider-has-to-support-iuserpromptservive/1648082
To avoid this problem, the option is to use VS 2019 until Microsoft releases an update of VS 2022 with the fix
Related
We have a set of performance and stress test written with the Microsoft Visual Studio Test Tools and recently those test stopped working on all but one of our virtual machines.
The virtual machine where the test is still working is still using “Windows Server 2016 Datacenter” while the virtual machines which don't work any more have been updated to “Windows Server 2019 Datacenter”.
There is also a slight difference between the used Microsoft Visual Studio. The working system us using “Enterprise 2019 Version 16.7.3” while the system which don't work use the slightly newer “Enterprise 2019 Version 16.10.0”.
On the machines which don't work any more we get the following error:
Could not run Web test 'XXXXX' on agent 'XXXXXX': Could not access table 'Test#csv' in data source 'dsTest' of test 'XXXXXX,XXXXXX': The OleDbParameterCollection only accepts non-null OleDbParameter type objects, not SqlParameter objects.
And I was able to pinpoint the problem to the following statement:
using WebTesting = Microsoft.VisualStudio.TestTools.WebTesting;
[WebTesting.DataSource (
dataSourceName: "dsTest",
providerName: "Microsoft.VisualStudio.TestTools.DataSource.CSV",
connectionString: "|DataDirectory|\\data\\Test.csv",
WebTesting.DataBindingAccessMethod.Sequential,
WebTesting.DataBindingSelectColumns.SelectOnlyBoundColumns,
tableName: "Test#csv")]
Are there any known problems when using Microsoft Visual Studio Test Tools on “Windows Server 2019 Datacenter” and/or “Microsoft Visual Studio Enterprise 2019 Version 16.7.3”?
And if so are there any fixes and workaround I could use?
Yes, there was a bug introduced in 16.10.#. Supposed to be fixed in upcoming release.
VS2019 1610-upgrade-breaks-MSTest-DataSource
I have legacy projects bound to Visual SourceSafe and done with Visual Studio 2003. Now, I have recently installed Visual Studio 2017 and TFS in the same machine.
Now when I try to open a legacy project that is bound to Visual SourceSafe I get a sequence of errors. Below the screenshots (pixeled for confidenciality reasons).
It seems like when open a legacy project (bound to Visual SourceSafe) with legacy visual studio 2003, it tries to connect to the TFS server (obviously it cannot). It is happening since I have installed new Visual Studio 2017 and TFS in the same machine, it seems like they cannot live together in the same machine. So how can I keep both VSS and TFS installed in the same machine? Is it possible?
UPDATED:
It seems like VS2003 does not allow to switch SCC providers. The only way is to hack the registry to switch.
I have found some interesting things that explains how to do it and it seems to work, the problem is that some links are broken, they are too old and not available anymore.
Source safe with Team Foundation Server in VS.2003
Installed TFS Version Control Provider and Now my VS 2003 Projects lost connectivity to VSS 2005?
MSSCCI Provider installation error
In above links it is provided a solution that consists on hacking the registry but the link they provide is broken:
Switch SCC providers
UPDATE 2:
As Edward Thomson has suggested in his answer, I have created a new key 'HKCU\Software\Microsoft\VisualStudio\7.1\CurrentSourceControlProvider\ ' and set it with a string value: ProviderRegKey="SOFTWARE\Microsoft\SourceSafe". Below screenshot, but it is not working:
MSSCCI is the Microsoft Source Code Control Integration API, it was the original API provided by Visual Source Safe for IDE tools like Visual Studio. Early Visual Studio versions (like 2003) only spoke MSSCCI, and expected a version control provider to provide MSSCCI. As a result, you can only have one version control provider speaking that protocol.
The Team Foundation Server client APIs provide MSSCCI (for Team Foundation Version Control only, not Git). As a result, if you want to use Visual Source Safe, you will need to configure Visual Studio to speak to that set of libraries instead of the TFS set of APIs.
In slightly more recent versions of Visual Studio (like Visual Studio 2008), you can choose your MSSCCI provider on the fly, in Options > Source Control > Plug-In Selection. All the MSSCCI providers will be enumerated and you can select between Visual Source Safe and Team Foundation Version Control.
If you're using an earlier version of Visual Studio that did not have this option, then you can change your MSSCCI provider by updating the registry directly.
Find the registry key:
HKCU\Software\Microsoft\VisualStudio\7.1\CurrentSourceControlProvider\
And set:
ProviderRegKey="SOFTWARE\Microsoft\SourceSafe"
Update 7.1 in the key with the version of Visual Studio that you have installed (Visual Studio 2003 corresponds to version 7.1.)
Once you have made this change, you will not be able to use Team Foundation Verson Control from Visual Studio 2003 without changing that back.
I am using SQL Server Data Tools (which = Visual Studio 2015 (Integrated)) and I am having trouble being able to connect to TFS. I can see the Team Explorer window, but when I click "Manage Connections" --> "Connect to Team Foundation Server" ....nothing happens. I get no error or prompt or anything. Has anyone else had issues like this? Spent most of my day googling the problem yesterday and I can't figure out what is wrong.
I cannot use VS community as I am part of a company and it would violate the TOS.
Unfortunately, TFS is not included in the minimal VS that SSDT installs. If you're not able to use VS Community due to license restrictions, I would suggest looking into the Express edition (Web or Desktop) of Visual Studio 2015. It has a less restrictive license and supports the SSDT tools.
I've been trying to install VS 2015 Enterprise edition on my computer but keep running into an issue. Hunting through SO for the last 24 hours, I've already tried the devenv.exe /ResetUserData & clearing the VS cache fixes, uninstalling enterprise edition and installing professional edition (which still failed for the same reason) and then reinstalling enterprise edition. I've tried deleting the .vs folder before opening the solution, ensuring that the MVC versions in the /Views/ web.config matches the version of the sites web.config (MVC 5.2.3.0).
As of this morning, I've noticed that it only crashes when I try to open a razor view that wasn't created through Visual Studio 2015 (I was using VS 2012 previously, and I'm trying to work on this project in 2015 now that I have a license). I can right-click in the solution explorer to create a brand new view and write anything I want in it with intellisense and save it, and open it back up without any issues.
I get the whole "An exception has occurred, this may be caused by an extension" message and then visual studio restarts if I try to open up a view that was already created through VS 2012.
I've tried looking inside of the log that it provides but I'm a newer developer so I can't really deduce anything from it..I'll attach it if anyone else can make anything of it.
MS VS Enterprise 2015 - Version 14.0.25029.00 Update 2 RC - .NET Framework Version 4.6.01055
I just cleared out the ActivityLog.XML and forced the error to get a fresh set of details - http://pastebin.com/j7RbGJFP
I found the answer in this blog post - https://blogs.msdn.microsoft.com/webdev/2016/01/12/visual-studio-keeps-showing-suggested-extensions/. It has to do with the extensions suggestion - it turns out if you have files not included in your project, you can't view them because of a bug introduced through the extensions suggestion. If you turn that off and include the views in the project, VS won't crash and you'll have intellisense.
I'm attempting to connect to TFS Preview from a C# application.
At the moment, I'm stuck trying to authenticate. I've added a reference to the TFS 2010 DLLs (I believe that these will enable me to connect, please correct me if I am wrong!) and my test case is as simple as. The URL I am trying to connect to is in the form https://MYSERVERNAME.tfspreview.com/DefaultCollection
var teamProjectCollection = TfsTeamProjectCollectionFactory.GetTeamProjectCollection(workPath, new UICredentialsProvider());
teamProjectCollection.EnsureAuthenticated();
This fails with the following exception.
Team Foundation services are not available from server https://MYSERVER.tfspreview.com/$/defaultcollection.
Technical information (for administrator):
TF400813: Resource not available for anonymous access. Client authentication required.
I had hoped that providing a UICredentialsProvider in the factory method creating the team project collection that it'd use this to provide authentication. The TFS Preview service uses Windows Live authentication, but I had hoped that this would be covered.
Pointers in the right direction greatly appreciated!
I have found that you cannot connect to TFSPreview using the TFS2010 DLL's, most likely because of the web credentials that need to be provided in order to access the site.
By adding a reference to the TFS2012 DLLs (which come with the Visual Studio 2012 RC at %PROGRAMFILESX86\Microsoft Visual Studio 11.0\Common7\IDE\ReferenceAssemblies\v2.0) I was able to successfully connect.
Download and install the Object Model for Team Foundation Server 2010SP1 and then install the Visual Studio 2010 SP1 Forward Compatibility GDR. Though this installer may look to only apply to Visual Studio 2010, it will happily update your Object Model installation if it's installed stand-alone.