Bob
|
| Posted: 08/03/2004, 5:22 PM |
|
I just trying this out for the first time time so bear with me. tried to create a simple editable grid using the builder and this is what I get :
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: Could not load type 'NewProject2.NewPage1.NewPage1Page'.
Source Error:
Line 1: <!--ASPX page @1-01A61258-->
Line 2: <%@ Page language="vb" Codebehind="NewPage1.aspx.vb" AutoEventWireup="false" Inherits="NewProject2.NewPage1.NewPage1Page" %>
Line 3: <%@ Import namespace="NewProject2.NewPage1" %>
Line 4: <%@ Import namespace="NewProject2.Configuration" %>
Source File: c:\inetpub\wwwroot\customerbase\NewPage1.aspx Line: 2
Any ideas on what I'm doing wrong? Using vb.net and the editable grid builder tool.
thanks
|
|
|
 |
bob
|
| Posted: 08/03/2004, 5:49 PM |
|
Added info.....
my publish setttings are:
C:\Inetpub\wwwroot\customerbase
http://localhost/customerbase
|
|
|
|
Stan
|
| Posted: 08/03/2004, 11:10 PM |
|
Bob
Please read the following article
http://support.codecharge.com/kb_article.asp?article_id=29
Stan
|
|
|
|
Bob
|
| Posted: 08/11/2004, 6:16 PM |
|
Still trying and unable to get this working. Here is the info for my settings:
I'm using Studio trial on XP Pro
path to vbc.exe is:
c:\windows\Microsoft.NET\Framework\v1.1.4322
path to website:
c:\inetpub\wwwroot\ForumProject
Using New/Project/FourmProject as a demo project I follow the steps and the project completes. Design, HTML, code and preview work fine. If I then use either Live page or Publish and then Live Page i get the Parser Error message after Studio completes the project build.
Under Tools/Options/Paths I have:
Default server path c:\inetpub\wwwroot
Default server URL: http://localhost
.NET SDK: c:\windows\Microsoft.NET\Framework\v1.1.4322
Parser error is:
Line 2: <xPage Language="VB" Codebehind=Deafult.aspx.vb" AutoEventWireup="false" Inherits="ForumProject.Default.DefaultPage" x>
Source file :c:\inetpub\wwwroot\ForumProject\Default.aspx Line 2
What am I doing wrong?
Thanks,
Bob
|
|
|
|
Mike
|
| Posted: 10/13/2004, 8:47 AM |
|
Stan:
The article that you suggested says to create a virtual directory, and I was able to do that. Then, the article says:
Once you setup the virtual directory, open the Project Settings window within CodeCharge and under the Publishing tab, specify the virtual directory path in the Server Path field.
So far, I have not been able to find the Virtual Directory that I created. It is there under the IIS Manager, but I can't find it and doing a search for it comes back empty.
Can someone help me with this? as I still can't get asp.net pages to run and am getting "Parser error Message: Could not load type 'Project4.NewPage1.NewPage1Page"
Quote Stan:
`
|
|
|
|
peterr
Posts: 5971
|
| Posted: 10/13/2004, 10:14 AM |
|
Mike,
When you view the properties of your Virtual Directory in IIS you should see the Local Path field in there. Just copy and paste its contents into the Server Path field in CCS.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
 |
|
kabilas
|
| Posted: 10/28/2004, 3:39 PM |
|
i have an interesting one. The published code works fine on the localhost/mydir.
However, when I move this to another server it does not work. I dont know where you can change the virtual dir path after the code has been published - it does not appear to be in the web.config.
I have confirmed that the server directory is a virtual directory
I have done this several time for various other projects - but this one is causing problems. I took this from the Taskmanager sample code
|
|
|
|
German Yemets
|
| Posted: 11/18/2004, 3:11 PM |
|
Just make sure that during creation of new subfolder, where later on you planning place aspx files, You did check out not only for project, but for solution too.
I had the same problems and this approach only help
Good luck German
|
|
|
|
Mikek
|
| Posted: 12/09/2004, 10:37 AM |
|
I am having the same problem/error. My codecharge studio projects were working just fine until I installed XP SP2. Since then, I cannot get any existing project to work nor will any new projects work. Any ideas what could have gotten fouled up? Virtual directory is in place and all paths appear to match. The compile appears to work and creates a dll with no error messages. Everything is on a local machine (my workstation): IIS, MSDE, CodeChargeStudio and browser of course. Visual Studio projects work fine, a recompile of DNN2 and IBS both work without error.
Thanks,
Mike
|
|
|
|
peterr
Posts: 5971
|
| Posted: 12/09/2004, 10:42 AM |
|
By the same problem do you mean that you also get the error "Parser Error Message: Could not load type 'NewProject2.NewPage1.NewPage1Page'." ?
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
Mikek
|
| Posted: 12/09/2004, 12:37 PM |
|
Yep, here is an example from the "taskmanager" example: Could not load type 'TaskManager.employees_list.employees_listPage'.
The crazy thing is, if I go to the individual page in the CCS and do a live page, sometimes it will work. If I then go to the page externally in a browser, it will work. If I close out the project and try this again half an hour later, it is back to not working. 
Mike
|
|
|
|
peterr
Posts: 5971
|
| Posted: 12/09/2004, 2:56 PM |
|
Please try this: in Project Settings -> Publishing, select the option "All files with extensions". Later press F9 to publish all the files.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
Mikek
|
| Posted: 12/13/2004, 7:53 AM |
|
OK, that worked..... But now another strange one has come up. Again using TaskMan as the project, Employees and Tasks will show the list and edit pages but Project and Status lists return an error page: InvalidOperationException: Queue empty. I have tried data connections to MDB as well as MSDE. Both produce the same result in CCS. Both tables exist and are populated and can be accessed by any other tool. VisStudio will produce a page that lists them both fine......
Thanks,
Mike
|
|
|
|
peterr
Posts: 5971
|
| Posted: 12/13/2004, 11:30 AM |
|
Mike,
What do you mean by "using TaskMan as the project"? You can only create own project based on that example. The example project itself should not be opened/used directly.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
Mikek
|
| Posted: 12/13/2004, 4:06 PM |
|
Peter,
Created a new project from the database, not the existing example project. Stored under c:\TaskManager\Taskman. Did a search on the forum and can't find any reference to the term "Queue empty" . Stack trace follows:
[InvalidOperationException: Queue empty.]
TaskMan.projects_list.projectsDataProvider.GetResultSet(Int32& PagesCount) +960
TaskMan.projects_list.projects_listPage.projectsBind() +355
TaskMan.projects_list.projects_listPage.Page_Load(Object sender, EventArgs e) +90
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750
Thanks,
Mike
|
|
|
|
peterr
Posts: 5971
|
| Posted: 12/13/2004, 4:27 PM |
|
I see. In this case I don't know the answer but feel free to contact the support if none of the users can help.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
FrankR
Posts: 154
|
| Posted: 12/15/2004, 10:58 AM |
|
Quote peterr:
Please try this: in Project Settings -> Publishing, select the option "All files with extensions". Later press F9 to publish all the files.
Man oh man, did I spend a lot of time today arm wrestling with this same problem. I found this answer in the forum, and it just worked. But ... why did I have to do this? What did we just *fix*?
_________________
FR |
|
|
|
peterr
Posts: 5971
|
| Posted: 12/17/2004, 11:15 AM |
|
This is due to technical reasons.
When publishing is set to "Project Files" then CCS knows which files to publish and when you select "Live Page" then it copies the current page to a temporary folder and publishes it, which includes compiling it in .NET. This works great in ASP/PHP, but results in only one page being compiled for .NET. Unfortunately such application doesn't know about other pages in the project.
However, when publishing is set to "All files with extensions" then CCS doesn't know which files may be included in the current page, so it copies everything from the project folder to the tempotrary folder and publishes it. This results in the whole project (Web site) being compiled, which is often needed for .NET, especially when you link to other pages.
We probably will disable the "Project Files" selection in the next version of CCS, when using .NET.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
