So I've found an article how asp.net 4.0 can skip handling of static resources (.css, .js, images), it mentions QFE extension for IIS, that is here. Problem is, that when I', trying to install it (on windows 7 x64), it says
The update is not applicable to your computer.
Love the obscurity of error message, I could think of several reasons why is this so:
I have it already (may be it was included in SP1, may be something else, file versions do not match with listed on update, my hwebcore.dll version is 7.5.7600.16385), but it does not work (how to check that?)
I has some dependencies, how to find out which?
Broken update on MS site, is there fixed version, how can i get it?
Other?
UPDATE: As I mentioned, dll's version is different from provided in hotfix page (my is 7.5.7600.16385 and theirs 7.5.7600.20654).
Looks like update is not needed (not sure why - because .net update/windows sp1/or smth else).
Update:
as long as I have production server with Win 2008 and IIS 7.0, update was required and installed successfully, so I don't have enough data, but it may that IIS 7.5 does not require that update anymore.
Related
We are for some time now trying to find a solution for server prerendering of SPA, specifically Angular4, for the purpose of SEO.
We have come to try and use aspnetcore-angular2-universal, which seems to be the perfect solution, however, we encounter problems deploying the published build to a local IIS server.
We have posted an issue regarding the problem on the issues page at which can be found here:
https://github.com/MarkPieszak/aspnetcore-angular2-universal/issues/491
We have followed the instruction under "Getting started" & "Deploy" (which can be found here: https://github.com/MarkPieszak/aspnetcore-angular2-universal) exactly but the error still exist.
The support is unresponsive on issues and thus we are posting also here.
The problem is (as mention in the issue linked here) that we get the following error:
Which indicates a problem with the web.config file. However the webconfig file is exactly as supplied in the starter project and seems also legit.
I should mention that building and running the project using npm build:prod and dotnet run works and we can lunch an in memory application from Visual Studio Code, however when taking the published folder to an IIS folder the error occurs.
Any help will be appreciated.
Did you installed .NET Core Windows Server Hosting bundle?
Check if AspNetCoreModule listed in IIS => Modules. Sometimes it not installed properly during #1, even if there was "Succeeded" at all steps. In that case I just removing it via Program & Features, and reinstalling it then.
Once I saw that error when manually copied web.config from sources over the publish folder. Problem is that original web.config contains placeholders like %LAUNCHER_PATH% and %LAUNCHER_ARGS%, which turns to appropriate values (dotnet and .\YourApp.dll for instance) during dotnet publish
Aperantly there were incompebilities between angular5 & universal in serverside.
The https://github.com/MarkPieszak/aspnetcore-angular2-universal seed was downgraded to using angular4.3 instead of 5. When we updated seed, the problem was solved.
I am using Visual Studio 2015 with ASP .Net MVC 6 on Windows 10. As far as I can tell everything's up to date, but I haven't changed anything recently that I know of. In the last couple of days Visual Studio has stopped letting me compare the current version of an *.cshtml file to see what changes I've made. It works for every other type of file I've tried, only these ones are being a problem.
I am getting the error message "Failed to start the configured compare tool." I've seen a couple of other posts (like this one: Visual Studio 2015 using Git unable to compare files and Microsoft Git Provider and Visual Studio 2012 failed to start the configured compare tool) but they seem to be talking about a more general cannot diff at all problem, which isn't what I'm seeing. It's almost as if git (or VS?) has decided to pick just this one file type to not like.
I have tried creating a new ASP .Net project with a new git repository and it sees the same problem, and the problem goes away if I rename the .cshtml file to give it a different extension. I've had a look in the .gitattributes file but can't see anything, though if I'm honest I don't really understand how git works beyond the basic 'this is how you drive it around when it works'. I've also tried removing and reinstalling everything git related I can find on my PC with no joy.
Anyone have any ideas on what I could have broken?
Update: I've just found this https://github.com/aspnet/Tooling/issues/293 which suggests that it might be related to an ASP .Net Update. Guess I'll probably have to wait and see.
Clearing the MEF cache appears to resolve this also. Close the IDE and delete the contents of this directory:
%LocalAppData%\Microsoft\VisualStudio\14.0\ComponentModelCache
Clear MEF Component Cache (Open VSIX Gallery) will probably do the trick as well.
Likely related to https://stackoverflow.com/a/32376450/1154135
This turned out to be related to a problem with the new ASP .Net tooling. They've apparently got a fix to be rolled out, but until then there is a workaround:
In the options panel, go to Options->Text Editor->HTML->Advanced
Set Identity Helpful Extensions to False
This is as per https://github.com/aspnet/Tooling/issues/293#issuecomment-161382206
Check your .gitignore file for references to .cshtml files. Dollars to doughnuts that something like *.cshtml is in that specific repo. Can you run the diff in git outside VS?
i have to fight against a strange issue in my company. we have 2 .net 2.0 (old, i know) apps, which start with an .asmx-file. the code-behind calls a c#-file, which includes a include abcd directive, whereby abcd originates from a 3rd-party company.
one app is in test and it works fine. the identical one is in production and fails with the error Could not load file or assembly 'abcd.dll' or one of its dependencies. The specified module could not be found.
when i look in the related web.config-files, none of them includes a pointer to abcd.dll, which i first do not understand in the context of the productive environment, where everything works. secondly when i look inside the \bin-folder, i see the related assembly/dll. again: this is identical in both systems.
the only difference of both systems is the fact that visual studio 2.0 (does this really exist?) is available on the test system.
please note: i am aware that assemblies have to be added via solution explorer in visual studio too. but i cannot do this as such an installation is not allowed here. but again: in web.config on the test server no reference can be found in the related web.config and everythings works fine.
so my question is: how to get this thing working in productive env?
thanks in advance
You may want to run Dependency Walker (depends.exe) http://www.dependencywalker.com/ and point it at to detect if any dependencies are missing.
I'd also look in the GAC (C:\Windows\assembly) to see if there are any related differences there.
Also, compare IIS setting on the two machines.
I'm trying to get started with ASP.NET/C#, and I'm doing so by following along some guides and tutorials.
One major issue I keep running into is that I have no Add Scaffolding in the context menu, nor Add Controller. I can't figure out a workaround for the lack of the Add Scaffolding.
There are various relate posts on SO. I will address some:
How to Add Controller
The accepted answer says something that directly contradicts my experience. There is no Add Controller option anywhere.
Reload the project
Reinstall suggested in this comment
I've tried uninstalling and reinstalling several versions. So far I've tried VS2013 Express for Web, VS2013 Community, and right now I'm using VS2013 Ultimate. Each one has had a fresh install installed within the month.
Add a guid
I tried adding a guid to a .proj file, an idea from another question at the moment of which I cannot find.
Same issue in Sep 2014, no answer
I realize there are several questions with the same issue, but none of the answers address my situation. Of the solutions I've seen proposed, I can't get any of them to work. Maybe I'm copying the guid's in the wrong place, maybe I'm not uninstalling correctly, I'm not sure.
I haven't yet tried to uninstall everything related to VS. I have a lot of random product on this machine. I wasn't aware that, for example, "Microsoft Visual Studio 2010 Tools for Office Runtime (x64) or Microsoft Visual Studio Tools for Applications 2.0 - ENU could disrupt VS2013 features. If anyone has information about this please let me know. I don't know the extent to which I would have to uninstall stuff in order to find the root of this issue. My Programs and Features menu is littered with MS product that I can barely tell apart.
EDIT:
Some Background Info:
I am using Microsoft Visual Studio Ultimate 2013 Version 12.0.31101.00 Update 4, and Microsoft .NET Framework Version 4.5.50938.
I used no special install instructions.
It's a web application. File > New Project... > Installed..Templates..Visual C#..Web..ASP.NET Web Application > MVC.
Upon Dleh's suggestion, I looked for the Add > ... buttons after changing the project type. I selected File > New Project ... > Visual Studio 2012 > ASP.NET MVC 4 Web Application (.NET Framework 4.5.1) > Internet Application, and I am confused to report that there is an Add > Controller... button. I have no idea what is happening.
Also, of note, I (within the week) installed VS2013 Ultimate on my home machine, and I have having none of these issues.
I believe I have solved the issue, but I don't know exactly what I did.
One answer from here was part of what prompted me to uninstall a number of MS products and features. Unfortunately, I can't remember the exact program or feature I uninstalled.
It seems like the uninstalling of related programs and features fixed the issue. By "related programs and features" I mean anything in the Control Panel > All Control Panel Items > Programs and Features menu that had ".NET" or "Visual Studio" or "Microsoft * Web Tools" or of the like. Many of them required a system reboot after uninstalling, and after one system reboot, the desired features in VS2013 was there.
There were on the order of 20-30 MS+VS+.NET related programs, and I uninstalled about 15.
I can't remember exactly which one I uninstalled, but it was anything that look remotely old and related to VS or .NET. Even if it was recent, I always figured I could reinstall stuff if I got the wrong thing.
Hopefully, anyone going through a similar issue will find this helpful. Good luck.
Had the same issue, installing
AspNetWebTools2013_1Setup.exe
WebToolsExtensionsVS.msi
fixed it for me.
Link Here
I am getting this error a lot:
Feature '{insert feature here}' cannot be used because it is not part of the
ISO-2 C# language specification
I am working on a .NET 3.5 website that I've worked on on and off for about two years. I've never seen this error before my most recent around of updates. I'm using a decent amount of LINQ coding throughout and I get these errors related to much of the LINQ code. Based on what I've read it seems like even though I'm using .NET 3.5, for some reason it thinks I'm using 2.0. But I can't find anything that says how to fix it.
One example of a problem is that if I try to add a new item to the App_Code directory, I do not get the option to add a LINQ to SQL dbml file.
If anyone can shed some light on how exactly I would fix this, I would much appreciate it.
I was unable to locate an "Advanced" option under the build tab. I have a feeling it is probably because it is a web app. I looked through the web.config and found 2 parts that may be important. Most things referenced 3.5.0.0 or v3.5. The settings are consistent with older backups of the web.config from when there were no errors. By the way, only intellisense and things within VS2010 are giving me problems. The website is running error free.
I have completed a total uninstall and re-install of VS2010 and I'm still having the same issue. I fired up my old install of VS2008 and I am NOT having this issue there. However, I would MUCH prefer to use VS2010 on this project.
I opened the website in VS2010 on my work computer, and there are no errors reported. This is making me think that there is something on my laptop that is causing the problem. As I noted above, I completely reinstalled Visual Studio 2010 and I am still having the problem. What does this leave? I have only one extension installed in VS, and it's the same one at work and on my laptop. Also, I did not reinstall the extension after reinstalling VS, and the problem persists.
Both PC's run Win7 Ultimate. Have VS2008 and VS2010 installed. VS2010 has the same extension installed on both. On my laptop I have the full version of SQL Server 2008 installed, but only the Management Studio on my desktop (we have a server in the office). Would SS2008 have anything to do with it?
Go to your project properties, the Build tab, Advanced - that should allow you to set which version of C# you want to use. It should default to the latest version supported by the version of Visual Studio you're using, but it sounds like at some point you've switched it to ISO-2.
(That's certainly true for Windows projects and class libraries - there may be a different location in a web app. In particular, have a look in Web.config.)
If this has only started happening recently, I'd have a look through your source control history at changes to any configuration files. Also try creating a new project of the same type, and see if that has the same problem.
Jon Skeet's answer is mostly correct. The location for the update is in the "Property Pages" which I got to by right-clicking on the name of the website, clicking Property Pages, the Build item, then target framework.
The extension I use, Solution Navigator, has it's own heading for the solution. Right-clicking on it DOES NOT give me the Property Pages option. By chance I right clicked on the title of the website under the solution heading and was presented with the Property Pages option. In there was the Build tab which contained the target framework option.
Once I finally found the target framework option, it was indeed set to .NET 2.0 for some reason. I changed it to 3.5, reloaded the solution, and now it works great.
Thanks a million Jon for your help and time working with me!!