I wrote a project, I ran cmd, to connect my codes to SQLserver. when I typed dotnet ef migrations add...; It said : that it can't find this 3.1.1 version folder despite the fact that when I asked the version, it would say it is 3.1.1 version.
So i downloaded the 3.1.1 sdk from Microsoft website, I installed it and nothing changed, the 3.1.1 folder wasn't added. I tried to find the folder but I could not.
Suddenly out of nowhere, I decided to download the framework instead. I opened it and it didn't need installation. I just copied this framework and replaced it with the whole dotnet folder which I had problems with😓. The problem started there, again I executed cmd and wrote dotnet ef... It said there is no ef. I again replaced the framework with another one, it said wrong machine, one another time and it said the dotnet image doesn't fit my pc or sth like this. I uninstalled the dotnet and installed it again, it now says an attempt was made to load a program with an incorrect format. I searched this error, they said I should change the 64bit iis to 32bit. I tried but I can't. Iis manager doesn't have the enable 32 bit option for me! And in the other ways folders are missing.
What should I do?
I solved it by first deleting the dotnet folder, then reinstalling visual studio.
Then I downloaded the dotnet sdk for runtime which is suitable for my computer
Related
When development is finished and TFS (VSTS) takes over. The build completes successfully and the artifact directory contains the published website via a build definition. The Release Manager is then triggered, and takes over and creates a website in an environment, the website files are copied to the environment and the website started. All good so far.
Missing the Database migration steps here...
Now someone starts the server and it fails because the database has not been migrated. How do we do that? The EF Tools were not copied to that environment, in fact we can't even run dotnet.exe because the core sdk has not been deployed onto that environment either. so even if we had the tools, we can't execute them.
In EF 6.x it was easy cause we could just copy migrate.exe as part of the artifacts, and run that on the environment after the files were copied. As I understand it, the EF Tools are now a DLL (ef.dll) that has to be run by dotnet.exe. Does this mean that all web servers now need Core SDK to perform migrations?
Other details about my project setup:
asp.net.core application being deployed onto a QA server for testing. This is not a dev box, does not have VS2015 installed, does not have Core SDK installed.
Update: EF.EXE is part of preview3 and 4.
This solves the requirement for "dotnet.exe" being installed. I can copy that into the artifacts drop like I used to with migrate.exe. Is this the proposed solution by the EF Team?
EF.EXE is part of preview3 and 4.
This solves the requirement for "dotnet.exe" being installed. I can copy that into the artifacts drop like I used to with migrate.exe. Is this the proposed solution by the EF Team?
Yes. Do this.
Also see issue #6313 where we want to make this experience a little easier on .NET Core.
In order to run .NET Core web application on your server, you need to install .NET Core SDK (currently 1.1) on your servers. Doing so will give you the dotnet command so that you can execute dotnet ef database update on your server environment to update the database to a specified migration.
I have written an application that I deploy via Clickonce, but I want to deploy it via Installshield, so I am experimenting with it. I found and downloaded dotnetfx45_full_x86_x64.exe, the redistributable for .NET Framework 4.5, and made a Installshield prerequisite from it. I wrote a simple application that has a RDLC report that just says “Hello World”, and it needs .NET Framework 4.5, and used Installshield to deploy it. The Reportviewer needs Microsoft SQLClrTypes_x86.msi and SQLClrTypes_x64.msi, and ReportViewer.msi, so I got those and made Installshield prerequisites from them. For the ReportViewer.prq, I specified SQLClrTypes_x86.prq and SQLClrTypes_x64.prq, as dependencies, and for SQLClrTypes_x86.prq and SQLClrTypes_x64.prq I specified dotnetfx45_full_x86_x64.prq as a dependency.
When I installed my little application on my test computer (running Windows 7), it installed the 4.5 framework, said it needed to reboot, and asked if I wanted to reboot now, and I clicked Yes. I was thinking it would reboot and continue the installation, but when it rebooted, that was the end of the installation. I ran setup again, it asked if I wanted to install the 4.5 Framework (it asked me the first time, too), so I clicked No. After clicking No, it installed the rest of my program, and it ran perfectly.
How can I get the installation to continue after it reboots from installing the .NET Framework 4.5?
Thanks
Here's a blog I wrote about 9 years ago:
Using InstallShield 12 to Install .NET Framework 3.0
It hasn't changed much. You want to use the prereq editor to change the reboot behavior to Note it, fail to resume if the machine is rebooted, and reboot after the installation.
Also please note that InstallShield consumes it's PRQ files from the ISProductFolder (C:\Program Files (x86)\InstallShield.... ) I don't care for this from a CM perspective. I recommend isolating the file and file references to relative paths based on ISProjectFolder and keeping all of these files in your source control tool.
Behavior Tab
I am trying to use Jint in my C# WinForms Application but NuGet is refusing to install the package. I can install other packages perfectly fine including this one called JavaScriptEngineSwitcher.Jint. I googled around and couldn't find anyone else with the same problem. The error says it has a problem with the .NET Framework version but it is my understanding that 4.0 should be just fine (even so, I played around with it but nothing worked).
https://www.nuget.org/packages/Jint/2.1.0
The package does work fine in .NET 4.0 packages. Make sure you have the latest update of the Package Manager console. If it is updated or udpating doesn't work, try restarting Visual Studio and try again.
I just downloaded and installed .net 4.5 and it went through the installer successfully, I got all the successful install messages, restarted my machine, and nothing.
My C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework was supposed to have a 4.5 folder in it now, and it doesn't. Also, I can't change any of my projects to 4.5 in visual studio, which I was supposedly able to do also. I followed Scott Hanselman's blog here and I'm not getting the same result.
Also, one of my interns did the same thing today and got the exact same result on his own machine.
Ultimately all I want to do is run EF 5 so I can get fricken enums! And I thought I had to have 4.5 to do that.
Thanks!
I'm trying to get up and running with nUnit, which has been pretty painful so far. I have successfully installed and added a reference to the nUnit framework, and I've successfully created a simple test--but get this error when I try to use the nUnit GUI:
C# .NET 4.0 Testing Framework?
On the advice of that post, I'm now trying to run nUnit from inside VS2010 with testdriven.net. I successfully installed testdriven.net, but when I re-start visual studio, I simply don't see the context menus described in the testdriven.net quickstart. How do I know if testdriven.net even installed correctly? What can I do to get up set up with testdriven.net or nUnit?
If you wanna check if it's installed, go to: Tools->Add in Manager, you should see it listed there.
If it's not there, then it is not installed, try the following:
try uninstalling from control panel 'TestDriven.Net 3.0 Personal', restart, then install again while visual studio is closed
make sure you download the RTM not the beta version, right click and unblock the zip file, install as admin.