Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 10 of 10
  1. #1
    Senior Coder DanInMa's Avatar
    Join Date
    Nov 2010
    Location
    Salem,Ma
    Posts
    1,577
    Thanks
    13
    Thanked 248 Times in 248 Posts

    noob ?'s re: application folder and app publishing

    hello all.
    I primarily use classic asp and vbscript in my current environment. I took a class on visual studio 2008 and I am working on my first hello world app in .net.

    my work server is iis 6.0with .net 2.0 enabled. I do not have admin access to it.
    I recently completed a test page and when I built then debugged the app it ran fine.
    When I publish it Im getting errors which google tell me is because I have nto set up the folder as an applicationj folder.

    Can somsone point me to an article on how to do so or explain what steps I need to take in order to setup the page.

    If i have to access the server, I'm curious if its common for you to have to do thigns that required server access often?

  • #2
    Super Moderator Inigoesdr's Avatar
    Join Date
    Mar 2007
    Location
    Florida, USA
    Posts
    3,638
    Thanks
    2
    Thanked 404 Times in 396 Posts
    What are the errors you are receiving? Often errors can be caused by permission issues on the site's folders.

    Quote Originally Posted by DanInMa View Post
    If i have to access the server, I'm curious if its common for you to have to do thigns that required server access often?
    Yeah, it's pretty common. Most server admins set up the server to be very restrictive, and IIS is setup to be pretty restrictive itself to minimize security issues.

  • #3
    Senior Coder DanInMa's Avatar
    Join Date
    Nov 2010
    Location
    Salem,Ma
    Posts
    1,577
    Thanks
    13
    Thanked 248 Times in 248 Posts
    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 the assembly 'App_Web_42ivdqoe'. Make sure that it is compiled before accessing the page.

    Source Error:


    Line 1: <%@ page language="C#" autoeventwireup="true" inherits="_Default, App_Web_42ivdqoe" %>
    Line 2:
    Line 3: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    googling has turned up that the folder hasnt been properly setup as an application folder

  • #4
    Senior Coder alykins's Avatar
    Join Date
    Apr 2011
    Posts
    1,662
    Thanks
    41
    Thanked 189 Times in 188 Posts
    can i see your C# call to the file?
    edit:
    not the whole code behind- just the call ref

    edit edit: and you said you are able to build this successfully? are you throwing an error publishing it or does that happen fine as well?

    I code C hash-tag .Net
    Reference: W3C W3CWiki .Net Lib
    Validate: html CSS
    Debug: Chrome FireFox IE

  • #5
    Senior Coder DanInMa's Avatar
    Join Date
    Nov 2010
    Location
    Salem,Ma
    Posts
    1,577
    Thanks
    13
    Thanked 248 Times in 248 Posts
    build goes fine no errors. I recently installed vs2010. built the solution then published to the live server without setting up any application folder( dont even remember hearing abotu this in class) . Works fine on the dev server. the only thing Im really doing here is using web.config to limit access to the folder to an active directory group Im in, which does work on the dev side.

    entire file is :
    Code:
    <%@ Page Language="C#" AutoEventWireup="true"  CodeFile="Default.aspx.cs" Inherits="_Default" %>
    
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head runat="server">
        <title></title>
    </head>
    <body>
        <form id="form1" runat="server">
        <div>
        hi there
        </div>
        </form>
    </body>
    </html>

  • #6
    Senior Coder alykins's Avatar
    Join Date
    Apr 2011
    Posts
    1,662
    Thanks
    41
    Thanked 189 Times in 188 Posts
    are you talking about site/application: ?
    I think that section is if you want to make it part of an existing site...
    are you running iis7?
    in iis you can have the default site (or whatever site you make) A) have it's sub apps/sites/whatever you wanna call them... if it is working in dev but not prod i would say it is what Inigoesdr eluded to (and you seem to be on same track of-) it is most likely restictions in iis... also you may need to make little tweaks to iis for your app

    I code C hash-tag .Net
    Reference: W3C W3CWiki .Net Lib
    Validate: html CSS
    Debug: Chrome FireFox IE

  • #7
    Senior Coder DanInMa's Avatar
    Join Date
    Nov 2010
    Location
    Salem,Ma
    Posts
    1,577
    Thanks
    13
    Thanked 248 Times in 248 Posts
    application, IIS6. I dont have access to the server environment and while they have .net installed it's technically unsupported because the person in charge of it has been there for years and theyve never dealt wit a .net environment so they dont know what to do with it .

    If i need changes on the server I have to have a pretty good idea of what needs to be changed so I can indicate that to them. Any suggestions on what needs to happen?

  • #8
    Senior Coder alykins's Avatar
    Join Date
    Apr 2011
    Posts
    1,662
    Thanks
    41
    Thanked 189 Times in 188 Posts
    honestly- I am horrible in iis... i know enough to be dangerous... i usually pass it on to my boss who runs the servers and all that happy fun stuff... sry hopefully someone else will be of more help

    I code C hash-tag .Net
    Reference: W3C W3CWiki .Net Lib
    Validate: html CSS
    Debug: Chrome FireFox IE

  • #9
    Super Moderator Inigoesdr's Avatar
    Join Date
    Mar 2007
    Location
    Florida, USA
    Posts
    3,638
    Thanks
    2
    Thanked 404 Times in 396 Posts
    I haven't run in to this error personally, but it looks like a problem in older versions of .NET 2.0(link). There is a workaround posted on that KB article as well as a hotfix, and it appears to have been fixed in .NET 2.0 SP1.

  • Users who have thanked Inigoesdr for this post:

    DanInMa (11-23-2011)

  • #10
    Senior Coder DanInMa's Avatar
    Join Date
    Nov 2010
    Location
    Salem,Ma
    Posts
    1,577
    Thanks
    13
    Thanked 248 Times in 248 Posts

    Thumbs up

    Quote Originally Posted by Inigoesdr View Post
    I haven't run in to this error personally, but it looks like a problem in older versions of .NET 2.0(link). There is a workaround posted on that KB article as well as a hotfix, and it appears to have been fixed in .NET 2.0 SP1.
    Ahhh. ok well that def helps. I'm already negotiating getting the .net version on the server updated to 3.5 - I would ask for 4 but I believe that will only run on IIS7

    ty Inigoesdr


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •