ASP.NET Master Page frameworkName: Value cannot be null error - asp.net

I'm going over some ASP.NET tutorials and the first one I'm looking at is how to make a Master Page. When I do create a master page, I get an error:
Value cannot be null. Parameter name: frameworkName
It occurs in the first line of my master page (MasterPage.master) and it's the default page that gets created- I haven't modified it at all:
<%# Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs" Inherits="MasterPage" %>
Could somebody tell me what is the frameworkName parameter and how can I get rid of this error? FYI: I'm using Visual Studio 2010.

This is a bug in VS 2010:
The reason you are seeing this error is that there are assembly references in the xaml which you are failing to resolve. There is a startpage.csproj in the same directory as the .xaml file. Please copy both to the new folder and open the project file in VS 2010. This should work.
http://connect.microsoft.com/VisualStudio/feedback/details/485162/edit-startpage-xaml-frameworkname-value-cannot-be-null
Here is master file that I currently have, so I would check for missing assemblies?:
<%# Master Language="C#" AutoEventWireup="true" CodeFile="Site.master.cs" Inherits="SiteMaster" %>
Can you also recreate the solution and import into the new .sln file ?

I encountered this problem when I converted a file based asp.net web application to an IIS website. After several minutes of trying to see what was wrong, I decided to close and reopen this solution and that solved it.

Related

Where to find the codebehind?

I'm new to ASP, just inherited a database application. I'm having trouble with probably the most basic thing... how the file structures are set up.
I've confirmed I've found the right .aspx file of the page I'm working on, but it's just the template. I am looking for the code that is behind that file.
The page starts with:
<%# Page Title="" Language="C#" MasterPageFile="~/print.Master" AutoEventWireup="true"
CodeBehind="Servicecallreport.aspx.cs" Inherits="CrisisSupportApp.Secure.Reports.BriefSummaryReport" %>
I've done a search for "Servicecallreport.aspx.cs" and "CrisisSupportApp.Secure.Reports.BriefSummaryReport" on the server and I get nothing.
Where should I be looking for these .asp.cs files?
Look for a version control system like git, subversion, or TFS. The code is likely in there. ASP.Net does not need to deploy those code files to the web server at all, but instead allows you to pre-compile them.
try:
(what ever your root is)\CrisisSupportApp\Secure\Reports\BriefSummaryReport.cs

Could not load type 'Pages_MasterPage'

I performed a "WebSite Publish" and the following error occured:
Could not load type 'Pages_MasterPage'.
I've searched the web and found that Post:
Master Page getting Could Not Load Type error when publishing
I am posting my question after making sure that the site folder is set up to be an application, therefore, the post didn't help me much.
The server I'm publishing on is 3.5 environment
Any help would be greatly appreciated.
I am new to this and don't know how to proceed.
Is not find the class of the page, and I do not see the CodeFile so this is probably missing
<%# Master Language="C#" AutoEventWireup="true"
CodeFile="Pages_MasterPage.master.cs" Inherits="Pages_MasterPage" %>
and make sure the Pages_MasterPage.master.cs exist - if not maybe you need to recreate this master page and not change or make manual the header and the files.

ASP.NET: Could not load type

I'm getting the following error:
Could not load type 'Intel.Intel'.
I copied my entire Visual Studio 2010 folder before I formatted my computer and I copy/replaced the same folder with this one after I installed windows again. I'm running this locally not on a host server. Anyone know what I'm doing wrong? I've search google and find many pages giving solutions for this, but none seem to fix my problem. Let me know if I need to provide anymore additional information. Thanks!
Update: Sorry I was unclear I copied the "Visual Studio 2010" folder from under my documents. I've installed Visual Studio 2010 Premium from my MSDN account.
Update 2: I also forgot that I was getting this error below before the Could not load type error. I fixed it by replacing the "~" with ".". The strange thing is that while that will seem to fix that error -- If I try locating the file through the "Pick Master.." option when retyping "MasterPageFile=" it will give me the path with the tilda and yet it wont work. I don't know if this helps identify the overall problem or not.
The file '/Intel.Master' does not exist.
And below notice the "~/Intel.Master" -- as mentioned above I can get rid of this error by changing that to "./Intel.Master"
<%# Page Title="" Language="vb" AutoEventWireup="false" MasterPageFile="~/Intel.Master" CodeBehind="Index.aspx.vb" Inherits="Intel.Index" %>
Found a solution.
I looked in IIS Manager and I found that my application was a folder icon and not an application icon. So I right clicked it and selected "Convert to Application". After doing this it solved that error and now I have another one. I feel however that this solution did "fix" the problem.
There are a bunch of registry settings that would be missing installing in this manner. Also there are components (shared) that are installed outside of the VS2010 folder.
Your best bet would be to re-install Studio in the usual (from media) route.
Based on EDIT:
The types that are missing look like they were previously stored in the GAC. Delete the reference in the project and re-create referencing the actual assembly file (DLL)
To add the reference back in to you project, open your project, drop down your solution folder, then your projct - find the references node, right click it choose add refernce, go to browse .net assemblies and or file tab depending on where the dll is, find your dll and double click on it.
Replace the CodeBehind By CodeFile and remove the namespace. before the Inherits class name. For example:
Wrong:
<%# Page Title="" Language="vb" AutoEventWireup="false"
MasterPageFile="~/Intel.Master" **CodeBehind**="Index.aspx.vb"
Inherits="**Intel.Index**" %>
Right:
<%# Page Title="" Language="vb" AutoEventWireup="false" MasterPageFile="~/Intel.Master" **CodeFile**="Index.aspx.vb"
Inherits="**Index**" %>
it works I promise

In Web application, could not load type? asp .net?

In web applicaiton, when i am running the asp.net project i am getting the error like :
Could not load type 'Com.ajSolutions.CosmacCRM.Web.EmpInserting'.
<%# Page Language="C#" AutoEventWireup="true" CodeBehind="EmpInserting.aspx.cs" Inherits="Com.ajSolutions.CosmacCRM.Web.EmpInserting" %>
can you help me thank you.
This is often a result of the compiled code not being found by the runtime.
The DLL may be missing. Or if it's compiled on the fly, the code itself may be missing. Or maybe the type itself doesn't exist in the code (possibly renamed or moved to a different namespace).

Error: "The file '/MasterPages/MainMaster.master' does not exist." (Yes, this file does exist!)

I just got a new desktop computer with Windows 7 Pro as the operating system. I installed Visual Studio 2008 on to this new computer and tried to open a previously existing ASP.NET 3.5 solution that displayed perfectly fine on my previous computer (this previous computer used the Windows XP operating system, IIS6, and IE7 browser). However, in Windows7/IE8, I’m receiving the following error:
Server Error in '/' Application.
Parser Error Description: An error
occurred during the parsing of a
resource required to service this
request. Please review the following
specific parse error details and
modify your source file appropriately.
Parser Error Message: The file
'/MasterPages/MainMaster.master' does not exist.
Source Error:
Line 1: <%# Page Language="C#"
AutoEventWireup="true"
CodeFile="default.aspx.cs"
Inherits="_Default"
MasterPageFile="~/MasterPages/MainMaster.master"%>
Line 2:
Line 3: <%# Register TagPrefix="SBLContent" TagName="SBLContentBlock"
Src="usercontrols/content.ascx"%>
Source File: /SBLWebSite/default.aspx
Line: 1
Version Information: Microsoft .NET
Framework Version:2.0.50727.4952;
ASP.NET Version:2.0.50727.4927
Please believe me when I tell you that the file ‘/MasterPages/MainMaster.master’ file does, in fact, exist.
In addition, this file’s location is properly referenced in the code (as indicated in Line 1 above), and as I said, was displayed properly by the browser in my previous computer. It might also be helpful to note that I’ve tried to navigate to other pages in this site, and this browser displays the same message for any and all master pages located in my MasterPages folder.
In summary, for some reason the browser cannot see any pages in the MasterPages folder. Can anybody tell me why I’m getting this error message when the folder and file is exactly where default.aspx says it is?
Thanks in advance!
I appreciate your response.
However, this issue turned out to be an IIS7 issue. The error message I described arose out of the distinction made in IIS7 between a "virtual directory" and an "application" (I don't know if such a distinction existed in IIS6). To fix this error, I opened IIS7, right-clicked on the virtual directory folder for this site, and selected "Convert to Application." I then refreshed the browser, and the error went away.
Sigh.
Two things to check:
When using "~" in a file path, make sure that the current application deployment believes the root directory is the same as it was before. (I've run into this sometimes moving an app from the VS Development Server and IIS.)
Make sure that the user account that the server is running under has permissions to access that directory. Since you just moved the code over from another computer and probably some intermediate storage devices, the security permissions may not be right.
the error comes on the web form like this
<%# Page Title="" Language="vb" AutoEventWireup="false"
MasterPageFile="~/Site1.Master" CodeBehind="add_drivers.aspx.vb"
Inherits="au_transport.WebForm1" %>
correction
<%# Page Title="" Language="vb" AutoEventWireup="false"
MasterPageFile="Site1.Master" CodeBehind="add_drivers.aspx.vb"
Inherits="au_transport.WebForm1" %>
Instead of the "~" I was able to simply change the directory to a relative ".." So, what I originally had that gave me the problem was something like: "~/MasterPage/TheMainMasterPage.master" and this caused me to get the same error message. Changing it to "../MasterPage/TheMainMasterPage.master" fixed everything for me.
I recently had to move my websites from one server(32 bit) to another server(64 bit). On the new server I experienced the file not found error "Parser Error Message: The file '~/Master.master' does not exist"
NB: some of my applications were built for x86, you still need to convert your website to an application :-)
Solution:
In IIS8, click Application Pool -> select an app pool eg DefaultAppPool -> click 'Advanced Settings' -> Under the 'General' section set 'Enable 32-Bit Applications' to 'True' -> Click OK
Refresh your website/webservice and that should do the trick
previous code:-
<%# Page Title="" Language="C#" MasterPageFile="~/admin.Master" AutoEventWireup="true" CodeBehind="outgoingform.aspx.cs" Inherits="OCS.outgoingform" %>
after code changed:-
<%# Page Title="" Language="C#" MasterPageFile="../ocs/admin.Master" AutoEventWireup="true" CodeBehind="outgoingform.aspx.cs" Inherits="OCS.outgoingform" %>
change the code from everywhere from "~/admin.Master" to "~/ocs/admin.Master"
previous code:-
after code changed:-
change the code from everywhere from "~/admin.Master" to "~/ocs/admin.Master"
OK, so this is old and it is 2021 but, the path for your mater page has ~/site name/MasterPage.master or similar.
What I did to fix and because I uploaded to the server all in same directory, remove this ~/site name/ leave the name of the master page IE: MasterPage.master and all is well. make sure master page in same directory as other pages. Done.
What I had after edit...
<%# Page Title="" Language="VB" MasterPageFile="MasterPage.master"
do this for all pages
no site name or ~/ etc. What a pain but once you realize it is just a directory issue which in retrospect should have been obvious from the start.. all better now. Site up.

Resources