imageresizer vs2012 response code 404 - visual-studio-2012

I get an HTTP 404 after installing imageresizer on windows 2008 server r2 x64. I installed the needed packages (e.g. IIS, Visual Studio) and tried to create an project. I didn't knew which type I should choose, so I choosed "empty project". I downloaded imageresizer and copied the needed library files to bin folder. I copied the Web.config in the document root directory. I then created a website with the IIS-manager and pointed the doc root directory to the project directory, where my Web.config lives.
I than started the webserver and tried to access the server using firefox. Anyways, I get an HTTP 404 response code with this request body:
Not Found
HTTP Error 404. The requested resource is not found.
Can anyone help please?

Oh...I missed to copy the Web.config file from the BasicIISExample Application. I'm just getting a warning about adding DiskCache or CDN support. Anyways, its working like a charm now. Awesome software. :)

Related

Umbraco - Error when trying to run 'IIS Express: Start Website' in Visual Studio Code

I've just downloaded and installed Umbraco, IIS, and IIS Express (installed the following extension IIS Express in VS Code: https://marketplace.visualstudio.com/items?itemName=warren-buckley.iis-express).
When I run 'IIS Express: Start Website' in the command line in Visual Studio Code I'm getting the following error:
The following site was not found in the configuration file: 'UmbracoCms.7.12.1-d9eb4dfc-b937-4ca5-b37e-a7b3ad857080'
Just wondered if anyone knows what might be causing this?
This extension has a hardcoded link to where IIS Express is installed.
Workaround - go to where IIS Express is installed (somewhere in program files), launch it manually and then this VS Code extension will work correctly.

ASP.NET Core app build to target Core 2.1 fails on IIS 10 server where Core 2.1 is installed

I have just setup up IIS 10 on a clean Server 2016 hosted server, and installed the following packages that I have gleaned should be on the machine to allow IIS to host ASP.NET Core applications:
aspnetcore-runtime-2.1.0-win-x64.exe
dotnet-hosting-2.1.0-win.exe
dotnet-runtime-2.1.0-win-x64.exe
I have installed my app straight into the Default Web Site and replaced all files in C:\inetpub\wwwroot\ with my app files. I also did assign the web site an app pool with no managed code, so that isn't my problem.
Last time my app was built with 2.0, and I installed the latest versions of the above packages, which I'm sure was 2.0, and the only error I had was that the command dotnet that IIS uses to invoke Kestrel to run the site, was not in the PATH env. variable
Now when I try and browse to localhost on the Server 2016 machine, it gives me the following error, found in the Windows event log:
Application 'MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE' with physical
root 'C:\inetpub\wwwroot\' failed to start process with commandline
'dotnet .\QuickDrive.Mvc.dll', ErrorCode = '0x80004005 : 8000808c.
Initially I tried with the same build as before, which was 2.0, and when I got this error, I rebuilt the app to target 2.1. Nearly every search result and relevant SO answer I can find suggest a version conflict, but now there should at least be no version conflict between the runtime and hosting package on the server. Maybe there are other version conflicts I am not aware of though?
At very least I'm asking for some advice on how to get more detailed diagnostic information, even if I don't get an answer that tells me straight what config options and versions to check on Windows and on IIS.
You have to install the Core SDK for whatever version you want to target in Visual Studio. Installing the runtime alone won't do the trick. You may have the restart Visual Studio afterward to see it in the list.
Here is a link to the SDK 2.1 download (the latest as of this writing).
I solved the problem by running dotnet myWesite.dll in PowerShell, and first I found that dotnet.exe was not in the PATH environment variable, and after fixing that, running dotnet myWesite.dll again gave me a meaningful error message that an assembly was missing because it had not been included when I published the website.
I faced the same error on the dev machine in IIS Express. MVC App stopped working all of the sudden. Eventlog gave the 0x80004005 error code.
After trying multiple suggestions, the solution to debug the wired error code was to run the app in the console:
[Project bin folder]> dotnet [projectname].dll
It appeared that during the NuGet package update, the dotnet core version was accidentally updated to 2.1.4 where as the installed version was 2.1.3
[could be a bug in Nuget manager as the update was from there]
I edited the project file to reference the available version (2.1.3) and the app started to work properly.

When switched from IISExpress to IIS error in asp.net core

I am trying to run my asp.net core application (1.0 , 1.1 or 2.0) using IIS instead of IIS Express. However, when I try to do that I get the following error message:
Unable to start process c:\Program files\dotnet\dotnet.exe. The web
server failed with status code 500, Internal Server Error
It does work with IIS express
P.S tried reinstalling the dotnet core and starting VS ad administrator
applicationhost.config has a lot of information in it, but the section I needed to change was under the sites tag. The physical path was set to the directory where the project was located on my other computer. I changed the path to match the path on my current computer and all worked fine. Not sure why this path isn’t relative one it exists within the solution. This is the line that I needed to change.
<virtualDirectory path="/" physicalPath="C:\Users\ericl\Source\Repos\ASP.NET Core Contacts\Contacts\src\Contacts" />
As an alternative it also works to close Visual Studio delete the whole .vs folder and reopen the project in Visual Studio. This causes the config file to regenerated with the proper values.
for more details

Visual Studio 2012 HelpViewer 2.0 still broken: location specified installing content invalid

Using HelpViewer local or try to Add or Remove Content from the VS2012 Help Menu always results in message:
The location you specified for installing Help content is invalid, or you do not have permission to access it.
I get the error using using VS2012 Update 3 as an admin, or using command line HelpViewer as admin.
So I think this is a 'specified location invalid' not a permissions problem. I check the registry, and
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Help\v2.0 AppRoot is C:\Program Files (x86)\Microsoft Help Viewer\v2.0\
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Help\v2.0\Catalogs ContentStore is C:\ProgramData\Microsoft\HelpLibrary2\Catalogs\
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Help\v2.0\Catalogs\VisualStudio11\en-US catalogName is Visual Studio 2012 Documentation
And the MSHC and METADAT files are installed at C:\ProgramData\Microsoft\HelpLibrary2\Catalogs\VisualStudio11\ContentStore\en-US
There is a discrepancy: what is the CatalogName? is it "VisualStudio11" or is it "Visual Studio 2012 Documentation"?
I even tried to repair VS to fix. First I used Control Panel Programs to remove HelpViewer 2.0. then I repaired VS 2012. The removal removed the HelpViewer app and files, and the repair restored them. I don't recall and did not note (my bad) changes to registry. But same ugly issue.
There are few related posts on the Internet, but I cannot find complete definitive information about the registry settings in relation to content and exe location
I finally found the registry documentation for Help Viewer 2.0 at:
http://msdn.microsoft.com/en-us/library/hh500508.aspx
I solved the problem by Editing:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Help\v2.0\Catalogs\VisualStudio11, setting the Key, LoactionPath, to the Value, C:\ProgramData\Microsoft\HelpLibrary2\Catalogs\VisualStudio11
Note that the .mshc, .mshi, .metadata files are located at:
C:\ProgramData\Microsoft\HelpLibrary2\Catalogs\VisualStudio11\ContentStore\en-US
In my case, I'm using Visual Studio 2019 Community Edition on Windows 7 and I have the same challenges when I configured my LocationPath previously to external drive and deleted it because I wanted to relocate it to C drive then, I got the same error messages; but I got the idea from here where it's located in Registry, so what I did is ... I remove this key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Help\v2.3
re-install the Help Viewer from Visual Studio Installer and it works; now i have to download everything again from the Web through Help Viewer as I wanted newer and updated version.
I wish this solution could also help someone looking for answers to the same challenges. Good LUCK! ^_^
This issue might prevail even if you update registry keys, add CatalogType.xml, etc. I solved this as below.
The shortcut for Microsoft Help Viewer was pointing to
"C:\Program Files\Microsoft Help Viewer\v2.0\HlpViewer.exe" /catalogName VisualStudio11 /helpQuery method=f1&query=msdnstart /launchingApp Microsoft,VisualStudio,11.0 /sku 3000
Note the version 2.0 and /catalogName VisualStudio11. This was the problem. I corrected the version to 2.1 and /catalogName to VisualStudio12 and updated the shortcut. Things started working.
"C:\Program Files\Microsoft Help Viewer\v2.1\HlpViewer.exe" /catalogName VisualStudio12 /helpQuery method=f1&query=msdnstart /launchingApp Microsoft,VisualStudio,11.0 /sku 3000
Helpviewer needs some command line parameters to start and incorrect parameters caused this issue.
In my case the problem (The location you specified for installing Help content is invalid, or you do not have permission to access it.) was that I at some point renamed the folder where Help content was located:
(external disk) I:\10 INSTALL PROGRAMI\Visual Studio\Help Content = current path
I:\10 INSTALL PROGRAMI**MS** Visual Studio\Help Content = original path.
So, after renaming ... \MS Visual Studio... into ...\Visual Studio..., the path was broken.
As per above answer (from 'subsci' user, thank you), I modified the path in Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Help\v2.1\Catalogs\VisualStudio12 -> LocationPath, and this solved the problem.
In my case (VS2019 Community Edition on Win10), the folder %ProgramData%\Microsoft\HelpLibrary2\Catalogs\VisualStudio15 was missing!
I created the folder but it still didn't work (complained that "A content file required by the Help Viewer is missing or has been corrupted"). I had to copy file "CatalogType.xml" from another version of VS i had on my PC to work. The contents of that file are the following:
<?xml version="1.0" encoding="utf-8"?><catalogType>UserManaged</catalogType>
Then Help Viewer 2.3 was opened and it just needed me to select the content to download.
In my case (VS2019 16.11.9) on my workstation I found that
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Help\v2.3\Catalogs\VisualStudio15 only had a key "VendorContent"=dword:00000001
I checked with my laptop (VS2019 help was working), and export the HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Help\v2.3\Catalogs\VisualStudio15 branch, and imported the reg file on my workstation - problem solved.
This is the content of the exported reg file:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Help\v2.3\Catalogs\VisualStudio15]
"LocationPath"="%ProgramData%\Microsoft\HelpLibrary2\Catalogs\VisualStudio15\"
"LastUpdated"="01/25/2022 20:01:00"
"VendorContent"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Help\v2.3\Catalogs\VisualStudio15\en-US]
"SeedFilePath"="C:\Program Files (x86)\Microsoft Help Viewer\v2.3\CatalogInfo\VS11_en-us.cab"
"catalogName"="Visual Studio Documentation"

Windows Store Apps: Visual Studio 2012 The system cannot find the path specified error?

I downloaded a sample Windows Store Apps project from the Dev Center samples site
When I run the project, I receive the following error in the CharmDemoGridApp
The system cannot find the path specified error
there are no more details, I tried to clean and rebuild the project and nothing happens.
what can be the reason of this ?
OK, I found that the reason was a missing referenced dll.
adding it correctly solved the problem

Resources