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.
Related
Long story short, I have an in-production project using VS 2019. I also have VS 2022 Preview installed for a future project. They're supposed to be isolated and run side-by-side (ha).
Sometime in the last two weeks, after what I think was an update to either Windows, VS 2019, or VS 2022, my in-production VS 2019 project refused to build.
I was able to isolate the issue to the nuget packages in the c:\Users\username.nuget\packages folder. Looks like on a nuget package install or restore, I just get a single file like numuvq1z.vdd
To test, I created a new console project in VS 2019 and installed the AutoMapper nuget.
I get only one file: C:\Users\username.nuget\packages\automapper\11.0.1\numuvq1z.vdd
If I do the same thing in VS 2022, I get the full nuget package installed.
So I uninstalled VS 2022 and repaired VS 2019 ... and the problem persists. So looks like nuget is broken in VS 2019, but no idea how to fix it.
The error I get is "The specified structure must be blittable or have layout information. Parameter name: structure"
Any ideas?
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 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.
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.
Four days ago I updated VS2013.3 to VS2013.4 and entity framework broke.
The error occurs immediately after compeleting the EF dialogue and adding
a table. The diagram displays and I get the error output:
Metadata file 'C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\Entity Framework Tools\NuGet Packages..\IDE\EntityFramework.dll' could not be found d:\users\allen\documents\visual studio 2013\Projects\WebApplication8\WebApplication8\Models\Model1.tt 1 1 WebApplication8
There is NO SUCH FOLDER on my C drive, which is a smallish SSD. I install everything I can on D. I've played with registry setting and system environment variables for VS120COMNTOOLS and nothing seems to work.
I've uninstalled and reinstalled EF, and VS2013.
I'd appreciate any assistance.
Thanks