I am trying to use OpsHub Visual Studio Migration Utility (Free Version) to migrate the Work Items in TFS2015 (Version 14.102.25423.0) to VSTS.
When I set the TFS server URL as Source EndPoint, I got the TF31002 error as shown in the following screenshot:
TF31002 Error when setting the Source EndPoint to a TFS2015 Server
I am able to connect to the TFS Server via all of my browsers and Visual Studio (2015/2017).
I tried some solutions like:
- clearing IE cache/cookies
- clearing TFS cache
- delete Visual Studio TokenManager folder on registy
Thanks in advance for any provided solution.
My machine is behind a proxy et here are the configuration in settings.properties:
action=update
installationLocation=C:\\Program Files\\OpsHub Visual Studio Migration Utility
httpHostName=my_proxy_ip_address
httpPort=8080
httpUsername=my_company_username
httpPassword=my_password
httpNonProxyHosts=localhost|127.0.0.1
useSameParametersForHTTPS=true
httpsHostName=
httpsPort=
httpsUsername=
httpsPassword=
httpsNonProxyHosts=localhost|127.0.0.1
It seems that you'll have to enable two of the OVSMU's processes to utilize the proxy configuration as done in the _JAVA_OPTIONS environment variable.
C:\Program Files\OpsHub Visual Studio Migration Utility\Other_Resources\Resources\TFSUtility\ovsmu.exe.config
C:\Program Files\OpsHub Visual Studio Migration Utility\Other_Resources\Resources\TFSUtility\TFSService\opshubtfsservice.exe.config
Open each of the above mentioned configuration file in a text editor (as an Admin) and un-comment the following XML node structure.
<!-- <system.net>
<defaultProxy enabled="true" useDefaultCredentials="false">
<module type="com.opshub.tfs.test.Proxy, opshubtfsservice" />
</defaultProxy>
</system.net> -->
Remove the comments and restart the tool, you should be able to connect to the end points then.
Related
I am trying to setup Entity Framework for Cache in Visual Studio 2022 Community Edition running on Windows Server 2022.
I am following the guide at https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GBMP_eframe#GBMP_efinstall.
devenv /setup - no issues
setup.cmd - fails "Installer.exe: #053 # 2022.09.19T12:09:15.0917142: TraceOps.ShowMessage: could not open registry key: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft.NETFramework\v4.0.30319\AssemblyFoldersEx
I created the Registry folder AssemblyFoldersEx, reran setup.cmd and it ran sucessfully.
I did not have the path defined in the installation notes so I created it C:\Program Files (x86)\Microsoft Visual Studio\2022\Community\Common7\IDE\Extensions\Microsoft\Entity Framework Tools\DBGen and copied the files (3 in total) as instructed.
I open VS 2022 and Try to select the data source. Cache is not showning.
Can someone please guide me on what I am missing.
Thanks.
I have DevExpress XtraReports v18.1.6 version and PostgreSQL 4 v3.3. Visual studio 2017 v15.3.3 and Windows 7.
Here is scenario: In my project, I have some reports writen in devexpress v17.2. I could not run those reports, because I could not download exactly that version 17.2, I install new 18.1.6. Then in Visual studio main menu "DevExpress" I click on "Project converter to 18.1.." and that action replace my old dlls v17.2 with new 18.1. After that I could run reports (see it in designer).
But problem is with databse connection. I created connection string with "XpoProvider=Postgres".
Every time when I want to get data in report, or rebuild result shema, or manage queries I get error:
Could not load file or assembly 'System.Threading.Tasks.Extensions, Version=4.2.0.0,...
I have that reference, exactly that version. Also I tried with new versions of threading.tasks but unsuccessfully.
My version of Npgsql.dll was 2.2.7, I tried with 3.2.5 (read from some devexpres documentations). Also tried with new 4.0.3.
Did anyone have a similar problem?
we had the same issue when using the DevExpress (18.1) Report Designer with Visual Studio 2017.
I know this might not be an ideal or the best solution but at least it worked for us:
I used ProcMon to determine where it was looking for that specific File, for me it turned out to be C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\hhfnlhs1.kna
I downloaded the NuGet Package for System.Threading.Tasks.Extensions from NuGet (https://www.nuget.org/packages/System.Threading.Tasks.Extensions/)
I unzipped the Package and stored the DLL at that path from step 1
I had to active "loadFromRemoteSources" in my machine-config (see https://learn.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/dd409252(v=vs.100))
I had to put another DLL from NuGet (https://www.nuget.org/packages/System.Runtime.CompilerServices.Unsafe/4.5.2) into that folder from step 1
That's it - now I can access the DB again.
I have setup my own nuget feed and have hosted that on our dev server.
When I try to push my packages from my local machine to dev machine as below:
dotnet nuget push C:\MyProjects\Common.2.0.0.nupkg -k myapi -s https://mydev.com/AENuget/
I get the error as:
Response status code does not indicate success: 405 (Method Not Allowed).
Now I have read and tried many settings like adding
<remove name="WebDAV" /> <remove name="WebDAVModule" />
Giving permissions to my nuget packages folder, adding app pool account but still I am not able to resolve this issue.
Secondly instead of pushing if I just copy my nuget package file to the package folder being hosted in our dev server and then in visual studio I add the new server source I get the below error:
[Package Source] The V2 feed at 'http://mydev.com/AENuget/Search()?$filter=IsLatestVersion&searchTerm=''&targetFramework=''&includePrerelease=false&$skip=0&$top=26&semVerLevel=2.0.0' returned an unexpected status code '404 Not Found'.
So looks like neither the push from nuget nor the copy is working. Looks like some permission issue which I am not able to resolve.
Would appreciate if someone can provide any inputs to this.
FYI: This works fine if I host this on my local machine.
The problems you are having seem to indicate you are having issues with the NuGet.Server and the system itself. These can be problems with the firewall, hosting configuration (IIS), or a wide variety of problems.
If you are on a very small team, you might just create a shared folder on a network server (with read/write access for the team). You can add the package source to Visual Studio by following this article. The source will be the UNC path to the directory (e.g. \\servername\path\to\nuget\folder).
NuGet.Server is a package provided by Microsoft and NuGet. This is used widely so I do not believe you have a problem with the package. If you encounter a specific problem, we may be able to help.
When adding the media services nuget package, VS 2015 is giving me errors about having no working folder mapping, then rolls back.
Here is an example of the message:
There is no working folder mapping for C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\lib\net45.
When I open the same solution from VS 2013, it works as expected.
Does anyone know how to resolve the error is VS 2015, or perhaps why it doesn't work there but does work in VS 2013?
(In VS 2015, I opened the solution by browsing to the sln file locally - not by retrieving the solution from source control.)
This is a known bug: https://github.com/NuGet/Home/issues/1004 Use Visual Studio 2013 for now. In the rush to get it out, Microsoft released a product that was not ready, even though technically this is a NuGet issue.
Not a long term solution, but I unbound from TFS, added the packages I needed, then rebound.
Try to unbound the solution and projects in TFS before updating the nuget packages.
To unbound try this
You should be able to avoid the error if you unbound from TFS. To unbound, go to File->Source Control->Advance->Change Source Control. Select the project and click on the Unbound button\link at top.
Whenever I try to add an entity data model in Visual Studio 2013 on Windows 8.1 I see the following.
Does anybody have an idea how to fix this? I see the dialog to specify a database connection appear for a split second then dissapears.
I found a solution. Go into view->Server Explorer and remove any "Data Connections". Then this worked again.
I solved it by doing the following.
Make sure the versions of MySql.Data, MySql.Data.Entities, MySql.Web dll files in C:\Program Files (x86)\MySQL\MySQL Connector Net x.x.x\Assemblies\v4.5 and C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PrivateAssemblies are the same.
Make sure your project references the same version of dll
In my case my
MySql connector was 6.9.6
C:\Program Files (x86)\MySQL\MySQL Connector Net x.x.x\Assemblies\v4.5 and C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PrivateAssemblies had it as 6.8.3
Project referenced 6.8.3.
After updating all versions with same dlls, now I am able to update the "Model from database"
Hope this helps someone
Edit: A few weeks after there was some windows update which again screwed up the settings. To resolve it, I had to re-run the My Sql Connector installation and My Sql for Visual Studio, it worked fine after that.
Delete all connections in the Database Explorer Window and in the ADO .Net wizard add a new connection. I was able to solve this problem this way.
you have to delete all other connection from server explorer and delete other connection ss web.config
I Had a similar problem, spent 2 days trying many solutions but I finally solved. I just had to :
- Install MySQL For Visual Studio 2.0.5
- uninstall and install MySQL Connector 6.9.9
Note: Please follow the order VS => Connector and respect the version.
Finally I faced other problem and solved by adding an empty emdx first then changing SSL Generate Template property from SSDLToSQL To SSDLTOMySQL
Install MySql for VS 1.2.9
Install MySql Connector 6.8.3
Add these Nuget Packages to your Project:
EntityFramework // 6.4
Mysql.Data // 6.8.8
Mysql.Data.Entities // 6.8.3
Mysql.Web // 6.8.8
In the Solution Explorer, edit App.config(Add or Replace):
<entityFramework>
<defaultConnectionFactory type="MySql.Data.Entity.MySqlConnectionFactory, MySql.Data.Entity.EF6" />
<providers>
<provider invariantName="MySql.Data.MySqlClient" type="MySql.Data.MySqlClient.MySqlProviderServices, MySql.Data.Entity.EF6" />
</providers>
</entityFramework>
rebuild and nothing more
For Anyone having this issue in VS 2019. This is what I did after a week long troubleshooting and googling, I just remove:
EntityFramework
MySql.Data.Framework or MySql.Data (or any other MySQL Nugget Packages you have added)
Then I re-install just this two in same order:
EntityFramework
MySQL.Data.EntityFramework
Then Update you entityframework section in app.config/web.config as follows:
I did not add default connection factory, I also remove version info from MySQL