I am using Microsoft Visual Studio Installer Projects to make a setup file for my C# app and when I install my app it says:
Failed to update database because the database is read-only
Here is screenshot of my database in Microsoft SQL Management Studio that shows read-only is false.
Here is screenshot of my database file in installer that shows read-only is false.
Yet after installing my app I get error above.
Any idea?
Solved
While comments above were helpful but easiest solution for me that didn't require lots of editing and coding was to change Application Folder path to outside of Program Files (86) folder something like this
C:\[Manufacturer]\[ProductName]
Here is screenshot of where to change that path and everything works fine now
Now it will install on path like C:\My_Company\App_Name where there is no permission restrict for system to access database file.
The packages in my project.json uses the node package manager. I add a new package via nuget to my Visual Studio 2015 ASP.NET 5 Beta 8 project.
When I'm on my home internet I can get download packages. However when I'm at the office I get the following error in my console if I add a new package:
PATH=.\node_modules.bin;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External;%PATH%;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\External\git
C:\Users\USERNAME.dnx\runtimes\dnx-clr-win-x86.1.0.0-beta8\bin\dnx.exe "C:\Users\USERNAME.dnx\runtimes\dnx-clr-win-x86.1.0.0-beta8\bin\lib\Microsoft.Dnx.Tooling\Microsoft.Dnx.Tooling.dll" restore "C:\PROJFOLDER\PROJNAME" -f "C:\Program Files (x86)\Microsoft Web Tools\DNU"
Microsoft .NET Development Utility Clr-x86-1.0.0-beta8-15858
GET https://www.nuget.org/api/v2/FindPackagesById()?id='AutoMapper'
Error: FindPackagesById: AutoMapper
An error occurred while sending the request.
In Visual Studio 2015 Solution Explorer:
I get:
Package restore failed
If I use nuget in a classic class library that doesn't use npm then I am able to download the same packages, so the issue seem to limited to npm
On researching the error it is listed as an issue on GitHub.
A workaround listed on the issue is to set a Windows environmental variables to my corporate proxy.
However I don't have proxy settings set in Internet Explorer.
My questions:
How do I determine the proxy I am using?
Is there an alternative way I can get it to work other than setting the environment variables. I tried the dnx.config workaround but it didn't work.
I use the laptop both at work and home. Is their a solution where I don't have to change settings between office and home?
If your internet works through Internet Explorer you can just add the following section to the machine.config located in the folder C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config
<system.net>
<defaultProxy useDefaultCredentials="true" enabled="true">
<proxy usesystemdefault="True"/>
</defaultProxy>
</system.net>
If you get a permission error saving the file, save it to your desktop and copy it from there back to the original location.
I tried creating an Azure project in Visual Studio 2012 Ultimate with a single MVC4 web role in it but got this error message.
The project itself after creating didn't contain the MVC4 role I wanted. I only found similar error messages for MVC2 and on my other computer it works fine.
The roletemplatedata.xml file is a file included in each Windows Azure project in Visual Studio (ie: Web Roles with MVC3, MVC4, WCF, ...). You should be able to find it under C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ItemTemplatesCache\CloudService.
If you can't find this file there is probably something wrong with the installation of the Windows Azure SDK (VS2012 tools). Try to uninstall every Windows Azure component, download the latest version of the full installer here (install the SDK link) and install it again. This should fix your problem.
I am trying to build a ClickOnce Windows Forms project (.NET 3.5 / Visual Studio 2010) on a Windows Server computer. (In an effort to automate the build process with Hudson CI.)
For signing the ClickOnce manifest I created a temporary key in Visual Studio, temp.pfx. I can successfully build and deploy the project from Visual Studio on my workstation. But when running MSBuild on the server I get the following error messages:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets(1970,9): error MSB3326: Cannot import the following key file: . The key file may be password protected. To correct this, try to import the certificate again or import the certificate manually into the current user's personal certificate store. [C:.hudson\jobs[...].csproj]
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets(1970,9): error MSB3321: Importing key file "temp.pfx" was canceled. [C:.hudson\jobs[...].csproj]
I tried all of the following questions and answers without luck:
Stack Overflow question Cannot import the keyfile 'blah.pfx' - error 'The keyfile may be password protected'
=> In my case, the error message does not indicate a name of a certificate store but says "the current user's personal certificate store" instead.
=> Even when trying the accepted answer with "Personal" as the container name (sn -i temp.pfx personal), it fails to parse the key:
Failed to parse the PKCS#12 blob in ALiS_TemporaryKey.pfx -- An internal error o
ccurred.
Stack Overflow question Using MSBuild to sign ClickOnce or assembly results in error MSB3321
=> I tried the accepted answer, but the key file cannot be imported because "Either the user profile is not accessible or the private key that you are importing might require a cryptographic service provider that is not installed on your system"
=> The same happens if I try to import the file by double-clicking it in Windows Explorer (RobinDotNet's suggestion)
Stack Overflow question Signing assemblies with PFX files in MSBuild, Team Build, and TFS
=> The OP of that question was unsuccessful with the above two answers, too, but unfortunately not even the answers that he got would help me:
Log in as the user that runs MSBuild on the build machine, manually invoke MSBuild, and then type in the password when prompted.
=> I logged in and ran msbuild myproject.sln but it would not even prompt me for the password.
What finally fixed it for me was making the account under which TFS Build service runs an administrator on the local machine.
=> The account that runs Hudson (more precisely: Tomcat) already is a local administrator. I tried to run MSBuild from a "Run As Administrator" command line even and would get the same error messages still.
Update: I tried to open the solution in Visual Studio on the same server and build it. I get the same error. When I try to re-import the PFX file in the project properties' Signing tab, it tells me "invalid password". If I try to import the very same file in the very same solution in Visual Studio on my workstation and provide the very same password, it is accepted.
Update 2: If I take an old temporary key which I had generated with Visual Studio 2008, it can be successfully imported in the certificate store of our server; any temporary keys I newly create with Visual Studio 2010 cannot be imported.
Update 3: I was able to create a new "temporary key" in Visual Studio on the server and use it both on the server as well as on my workstation for signing the ClickOnce manifest. I only cannot make up a reasonable explanation for it - both computers are 64-bit, and I am using Visual Studio 2010 on both. Both have the v3.5 and v4 (4.0.30319) .NET framework installed. My workstation is a Windows 7 Professional, and the server is a Windows Server 2008 R2 Standard.
Copy the PFX file over to the machine you are doing the builds on. Double-click on it, and install it in the certificate manager on the machine. Be sure you are logged into the account used to do the builds.
Other suggestions/questions: Do you have the right version of .NET installed on the machine? Do you have privileges to write to the certificate store on that machine?
If you open the Visual Studio project, go to the project properties and try to create a new certificate, does it work? It should create a PFX file and add it to the project. And can you see it in the certificate store (menu Start/certmgr.msc)?
I found that if you create a temporary.pfx file and leave the password EMPTY then it will work fine on the build machine. I didn't realize that you could leave it empty and the first time it failed as for OP. Created a second temp.pfx with no password and it built on the build server for me.
I had totally the same issue. And fixed it by installing Windows SDK 7.1 for .net 4.0 on the build machine.
PS At first we've installed SDK 8.0A, and build was working fine except for singing. It seems, 7.1 updates some components in the system, so pfx begins to work.
I had same Problem, couldn't import on TFS machine. Turns out I had to export it on developer machine (project properties, signing page, click on more details)
in more detail -> tab details and then just export with a password. Copy that exported file to TFS and use same password: done
I have installed TFS 2010 including Build Service on a Win Srv 2008 R2 machine, and it works - almost.
What I can't seem to get going is the build using tools like resgen.exe from the Windows SDK - I get an error:
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets
(1835):
Task could not find "Resgen.exe" using the SdkToolsPath
"C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.0A\Bin\" or the
registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SDKs\Windows\v7.0A". Make sure the
SdkToolsPath is set and the tool
exists in the correct processor
specific location under the
SdkToolsPath and that the Microsoft
Windows SDK is installed
OK, so I went and downloaded and installed the most recent Windows SDK - v7.1. Everything went fine, I now have a copy of resgen.exe present and all - but I am still getting the same error.
OK, so I went and inspected the MSBuild targets file (c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets) mentioned in the error message - and I see it's using lots of references to FrameworkSDKDir and _TargetFrameworkSDKDirectoryItem - but where are those values initially set (to an obviously wrong directory, in my case) ?? I can't seem to find the "core" targets file and tell it to use my \SDKs\Windows\v7.1\Bin directory (instead of the \SDKs\Windows\v7.0A\Bin it wants to find - there's nothing in there...)
I think that the real problem is integration of the SDK v7.1 with VS2010.