Tech Off Post

Single Post Permalink

View Thread: Newbie need walk through publishing ASP.NET app--I show screenshots
  • User profile image

    PJL said:
    W3bbo said:

    Right W3bbo.  I could slog through all that.  But wait I have a better idea.  You are the person I need to do all of this in a flash--probably without even thinking twice--send me an email quoting a price to rent from you please to:  I am a poor Greek in a bankrupt country so any concession you could make on price would be greatly appreciated.  I actually do have a guy I am using in the USA (he helped load one of my Silverlight apps, which ran for about a week before somehow the permissions changed on the folder it was running on and now it's inaccessible), and he's earnest, but lacks experience with programming and appears very overworked.  I rather just use you.  Also I need to be able to run databases on occasion in SQL Server Express.  BTW I figured out a trick the other day where the database, though a trick in the connect string ("Data Source=|DataDirectory|UserData"), can reside in a subfolder in the folder your database app runs in, which makes maintainace easier I imagine because you don't have to copy the database into a central depository, but I digress.


    You mention web config file, and once I did have to play with the switches and XML in one such file when I was doing a login page for ASP.NET, so I do have a vague understanding of the same, but below is a simple "Hello World" Web.config file, and as you can see it's quite complicated looking (to me).  A lot of this stuff is signing off on your executables with a public key so they can't be spoofed I think, and other such stuff, but to me it looks pretty daunting.  There's a gulf between theory and practice that you, having mastered both, can bridge.  I myself was tickled pink the other day when I managed to build and then consume a 'web service' following an example in a textbook.  But getting such a web service to run outside of localhost might be another matter (maybe not, with your help)?!





    <?xml version="1.0"?>





                                  <section requirePermission="false" allowDefinition="MachineToApplication"/>


                                          <section requirePermission="false" allowDefinition="Everywhere"/>

                                          <section requirePermission="false" allowDefinition="MachineToApplication"/>

                                          <section requirePermission="false" allowDefinition="MachineToApplication"/>

                                          <section requirePermission="false" allowDefinition="MachineToApplication"/>









                Set compilation debug="true" to insert debugging

                symbols into the compiled page. Because this

                affects performance, set this value to true only

                during development.


                   <compilation debug="true">


                                  <add assembly="System.Core, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

                                  <add assembly="System.Data.DataSetExtensions, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

                                  <add assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3845AD364E35"/>

                                  <add assembly="System.Xml.Linq, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>




                The <authentication> section enables configuration

                of the security authentication mode used by

                ASP.NET to identify an incoming user.


                   <authentication mode="Windows"/>


                The <customErrors> section enables configuration

                of what to do if/when an unhandled error occurs

                during the execution of a request. Specifically,

                it enables developers to configure html error pages

                to be displayed in place of a error stack trace.


            <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">

                <error statusCode="403" redirect="NoAccess.htm" />

                <error statusCode="404" redirect="FileNotFound.htm" />





                                  <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3845AD364E35"/>

                                  <add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3845AD364E35"/>




                           <remove verb="*" path="*.asmx"/>

                           <add verb="*" path="*.asmx" validate="false"/>

                           <add verb="*" path="*_AppService.axd" validate="false"/>

                           <add verb="GET,HEAD" path="ScriptResource.axd" validate="false"/>








                           <compiler extension=".cs" warningLevel="4">

                                  <providerOption value="v3.5"/>

                                  <providerOption value="false"/>





            The system.webServer section is required for running ASP.NET AJAX under Internet

            Information Services 7.0.  It is not necessary for previous version of IIS.



                   <validation validateIntegratedModeConfiguration="false"/>



                           <add preCondition="managedHandler"/>







                           <add verb="*" path="*.asmx" preCondition="integratedMode"/>

                           <add verb="*" path="*_AppService.axd" preCondition="integratedMode"/>

                           <add preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd"/>




                   <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">


                                  <assemblyIdentity publicKeyToken="31bf3845ad364e35"/>

                                  <bindingRedirect oldVersion="" newVersion=""/>



                                  <assemblyIdentity publicKeyToken="31bf3845ad364e35"/>

                                  <bindingRedirect oldVersion="" newVersion=""/>






    uhm, okay...


    I've added your address to my Messenger contact lists, we can talk things over from there and see if we're suitable for each other.