image image Home   About   Downloads   Support   Links   Contact  
image





Copyright
2002 - 2013
Atozed Computer
Software Ltd.

image
Buy Online   Download Support  FAQ Questions
Atozed Home  »  Archive  »  IntraWeb  »  FAQ  »  Archive

IntraWeb .NET issues


You are now reading archived content.
Content in this area may be out of date, but is provided for archival purposes.


Where can I find Intraweb for Visual Studio .NET?

We no longer sell this version of the product. We continue to support existing customers but do not provide new versions.

I'm trying to upload a 10 MByte image to my server using IntraWeb's IWFile component, but that does not seem to work if using IW's assembly deployment mode. Does IntraWeb have any file size limitation?

No, but ASP.NET does have a default maximum of 4 MB for uploads. To adjust that you need to update your web.config file:

  <configuration>
    <system.web>
    <!-- This setting is important if your application offers huge up- or downloads -->
      <httpRuntime
         <!-- This is the size in KBytes, that ASP.NET will transfer max for any request/response. Default is 4096 KB -->
         maxRequestLength="50000"
         <!-- This is the period in seconds, that ASP.NET waits maximum for any request/response to be processed. Default is 90 secs -->
         executionTimeout="360"/>
  

 

I have Windows XP Home Edition. I have installed Intraweb for .NET, but I am unable to create executables for IIS. Why is this and what can I do?

StandAlone mode is the easiest solution when developing on XP home.

If you wish to test ISAPI with XP home you will need to install IIS. Windows XP Home Edition does not ship with support for IIS. But there is a solution for running IIS on Windows XP Home:  http://www.15seconds.com/issue/020118.htm .  


When I deploy my assembly to IIS and try to start the application I get "This session ID does not  belong to this process".

This is a common problem caused by virus scanners installed on the server. Norton AntiVirus is confirmed to cause this symptom, and others likely do as well. To solve this, exclude the assembly and web.config files from scanning.

More Information