Ok, read a lot of questions about this, but really didn't see any solution that works for me... So, any help will be very apreciated.
I'm running a MVC3 web application with Ninject installed through nuGet (so i got Ninject version 3.0.1.10). Everything works great, except for when i deploy it to the hosting service (LocaWeb.com.br).
Running the web App from there, i got the "System.Security.SecurityException: Request failed."
And the stack trace shows lots of ninject's calls.
So i read somewhere that i should be using a Medium Trust Ninject version, wich I downloaded (ver 3.0.0.15 for Medium Trust) but i really don't have a clue on how to install it manually over the nuGet installed version, or even if this is the right path to go for solving the problem...
Really lost here. :-/
Just replace the Ninject.dll from NuGet with the Medium trust dll when you deploy your application.
Related
Today I have been battling with a very odd issue. I spend my days developing an ASP.NET MVC3 web application that used to be ASP.NET 4. It not is now half MVC3 and half ASP.NET 4 all running under the same application. This is all fine.
Today we set up a brand new staging environment (Server 2008 R2), deployed the code and ran the app. Only to get HTTP 404 errors when trying to access any MVC page, all aspx pages worked fine. To prove that the issue was environmental we deployed the same code to a new application on the development box and this worked without a hitch.
After spending all day making sure both environments were exactly the same (IIS Role Services, Windows Updates, Installed Applications.. everything) I then noticed on the 404 error page that the Handler for the request was "StaticFile".
After a bit of googling I came across the option in the title
<system.webServer><modules runAllManagedModulesForAllRequests="true"></modules></system.webServer>
This now works, so I assume the modules used for none static routes isn't being called without it (forgive me if I’m being naive).
The thing is, on our development environment, the web.config doesn't have this attribute.
So why does it work without it on one server and not on another. Surely its less efficient to be calling all modules for all requests.
If anyone has any idea's to why this might be happening I would be eternally grateful, as although our staging environment now works, i hate not knowing exactly thy.
thank you!
The first thing I would check is to ensure that the following update is applied to your new brand new staging environment as it may have already been applied to your existing development environment and would explain why one environment is working and one is not: http://support.microsoft.com/kb/980368
For more information about static file routing, the hotfix above and general "how does extensionless routing" work, I recommend reading the following article: http://blogs.msdn.com/b/tmarq/archive/2010/04/01/asp-net-4-0-enables-routing-of-extensionless-urls-without-impacting-static-requests.aspx
Environment: I am working on a site in ASP.Net 2.0 running on IIS6; I am developing locally on WinXP which runs IIS 5.1, using VS2005 and VB.
Issue: I am trying to create caching for some business layer objects (actually creating a caching layer) using System.web.caching.cache. This should be available under System.Web namespace but all that I seem to have access to are: AspNetHostingPermission, AspNetHostingPermissionAttribute and AspNetHostingPermissionLevel (I have a reference to System.Web in the project and imports in the class). There are quite a few other classes (e.g., HTTPRuntime) which also do not appear (this is per the "Using SQL Cache Dependencies" tutorial http://www.asp.net/web-forms/tutorials/data-access/caching-data/using-sql-cache-dependencies-vb).
I'm at the end of my rope and can't seem to find anything out there to explain this. Has anyone been in this situation and seen this before? Any help getting this solved is MUCH appreciated!
OK, so not sure why I didn't think of this before but I checked the references tab under the project properties. In the list for System.web, the additional namespaces were unchecked; checking System.Web.Caching and recompiling fixed the issue.
Sometimes you're just toooooo close to something to realize the easy answer.
I've just started checking out WebMatrix, and am running into a problem. I performed a fresh install of WebMatrix, then started a tutorial which involves creating one small cshtml file. Whenever I try to run the site, I get the following error:
This type of page is not served.
Description: The type of page you have requested is not served because it has been explicitly forbidden. The extension '.cshtml' may be incorrect. Please review the URL below and make sure that it is spelled correctly.
Requested URL: /Home.cshtml
In the IIS Express Requests section, the page request shows the following error:
404.17 Dynamic Content Mapped to Static Handler
Details: The requested matched a wildcard mime map and was matched to the static filder (What's up with all the typos MS?) handler. However, if the pre-conditions were different, the request would map to a different handler. This can mean that the pre-conditions are incorrect.
I tried reinstalling to no avail. Does anybody have any ideas?
I am running Windows 7 Pro, with IIS 7 installed. (IIS Express is supposed to be able to run side-by-side no problemo)
Thanks much!
It was set to 4.0 -- Uninstalling and reinstalling ASP.NET Web Pages did the trick.
It seems you selected 2.0 .NET framework in Settings section (in WebMatrix). Change it to '.NET 4 (Integrated)'.
Same boat - just toying with it and its "integrated workflow" with VS2010..but alas, it's not as "clean" as one would hope (or maybe just needs more manual tweaking of knobs and switches).
But try this (instead of, or before giving up all hope and re-installing): run Webmatrix in Administrator mode (right click -> runas).
Your solution is something I had to do on the server side though (IIS6/w2k3)....via web platform installer. While it seems odd to install Webmatrix server side, I just gave up and did it anyway to ensure all the dependencies are installed along with it (didn't want to spend or rather waste any more time figuring it out).
Worked for me....after looking glassy eyed with that "but it was working fine yesterday" look. So I hope this saves you (and anyone else) some time and frustration.
I have a WP7 project in VS2010 pro/ultimate and I have added a web reference from another project on the same solution. The web service project is just a normal website project, I just created .ASMX file. I tested the service using web browser and it works fine.
The problem is, after I added this service as service reference, I cannot reference it in my WP7 project and I can't view it in Object Browser either as if it doesn't exist.
I use local URL like 'http://localhost:12345/WebService.asmx' when I added the service, VS can see all the methods and can add successfully. Very strange for me and I don't know how to solve this issue.
Anyone can give me any clue on this? Thanks very much.
I've had a similar issues before- on one machine, a restart was required, on another, I had to uninstall ALL of my SL stuff, then uninstall Vstudio, then reinstall and reapply any SL add-ons.
Then it worked fine.
Also had a friend with the same issue- uninstall all, then reinstall worked for him also.
I believe these were machines with pre-rtm SL and Phone bits on them.
I've had a similar problem. I created a WP7 project using VB.Net. I built a WCF Class web service, a client side proxy class, and then a WP7 application with the service reference. When I added the service reference, the code generating utility would not build the required Reference.svcmap file detail (it only created the header information). However the project would still compile, yet I couldn't reference the service in code as it didn't exist in the underlying files.
I tried recreating the WP7 project in C# and everything worked. My guess is that the VB implementation of WP7 might still have some issues, however that is a guess only. I'm keen to see if anyone else has had the same issue specific to the VB WP7 template or if it is something else.
I bumped into the same problem, but it was fixed after a reboot as suggested in this thread by dethSwatch.
I do remember that a silverlight SDK update was installed a bit earlier, maybe the reboot is required after the update?
I think this issue might be related to the January Update to the WP7 tools. I managed to fix this issue by installing the VS10-KB2486994-x86.exe fix found on the above page. That sorted the issue I had with generating a client side proxy for the WCF service I wanted to call. Hope this helps.
I am trying to get started in development of my website and plugins using Umbraco. When I download the binaries from Codeplex, the installation and running of the website works fine. When I downloaded the source code, All I get is a login screen even when the web.config files are the same. Am I doing something wrong or is there something I missed.
The path I use to map IIS to is
branches\4.1.0\umbraco\presentation
You need to compile the source code to get it to work.
To be honest, you shouldn't need the full source unless you really want to start hacking around in the core (which may cause you problems with future updates) or you want to see how stuff works. The Umbraco framework is pretty extensible, I've not found too much so far that I couldn't do without having to touch the core source.
I had a similar issue when running the source and that was that the hashing of the admin password did not work. So i debugged it to see what value was expected and then changed it in the database.