Free 6 months hosting on Discount ASP
 
  Forum  Core :: SDK (Vi...  Developing the ...  Deploying Visual Web GUI in shared Hosting Env
Previous Previous
 
Next Next
New Post 1/10/2009 11:10 PM
  darshanmarathe
23 posts
No Ranking


Deploying Visual Web GUI in shared Hosting Env 

Dear All

Is there any way to deploy the Visual Web GUI Application in a shared hosting environment where we can't register .wgx and .swgx extensions with the IIS Server.

As my hosting is shared hosting and when I asked send them the article they said we cannot do this changes to the IIS 

So any suggestion or I have to re-write whole application in the asp.net which will be dam pain full for me

 

Regards

Darshan Marathe

 

 
New Post 1/11/2009 2:20 AM
  palli
6034 posts
1st Level Poster




Re: Deploying Visual Web GUI in shared Hosting Env 
Modified By ori.cohen  on 1/11/2009 6:22:11 AM)

Hi Darshan Marethe,

You can change the .WGX extension with very minimal changes. As you can't have your shared hosting make such changes, you will have to select one of the allready correctly registered extensions (.aspx, .ashx ...).

This is from an earlier post, posted by Ori (which you can see HERE):

You basically need to do the following to change the VWG "*.wgx" extension to "*.aspx":

Add the following element inside the <WebGui> section of your Web.config file:
<Extension Value=".aspx"/>

Change the following element:
<add verb="*" path="*.wgx" type="Gizmox.WebGUI.Server.Router,...
/>
to:
<add verb="*" path="*.aspx" type="Gizmox.WebGUI.Server.Router,...
/>

Change the project default start-up page's extension to ".aspx".

That's it.

If you have a problem running your application this way, your hosting service provider may have  configured their IIS server to prohibit this action. In this case you can use the ".ashx" extension the same way.


There were some problems with some shared hosting and security, that might affect you (see HERE), that were fixed in 6.2.3, so in case those problems affect you, you should consider upgrading to 6.2.3.

There have also been some problems reported (see HERE) if you select the .aspx extension for your app and at the same time will be using that extension for some .aspx pages outside of VWG. In that case, consider selecting one of the other extensions for VWG, like .ashx.

Palli

 


Páll Björnsson - Visual WebGui support team - Email: support@visualwebgui.com
 
New Post 1/11/2009 2:21 AM
  ori.cohen
3521 posts
1st Level Poster




Re: Deploying Visual Web GUI in shared Hosting Env 

Hello Darshan Marathe!

You basically need to do the following to change the VWG "*.wgx" extension to "*.ashx" or ".ascx" or ".asmx" or "asax":

Add the following element inside the <WebGui> section of your Web.config file:
<Extension Value=".ashx"/>

Change the following element:
<add verb="*" path="*.wgx" type="Gizmox.WebGUI.Server.Router,... />
to:
<add verb="*" path="*.ashx" type="Gizmox.WebGUI.Server.Router,... />

This way, you application will not interfere with other applications running from the local IIS and you will be able to access your application without having to change the extension in the IIS.
From that moment on, you will be able to access your application only using the extension you provided.

If you need this also for VWG Silverlight, please reply.

Regards,

Ori Cohen
Manager of support, the Visual WebGui team

 
Previous Previous
 
Next Next
  Forum  Core :: SDK (Vi...  Developing the ...  Deploying Visual Web GUI in shared Hosting Env
Most promising startups
Top 3 most promising startups in 2009
   AJAX Framework | Web Development | Cloud applications | RIA Development | Silverlight Applications | Legacy Migration
The most popular open source Ajax applications framework for enterprises | Sitemap | Terms Of Use | Privacy Statement
Copyright © 2005-2009 Visual WebGui®    Design By: Template World
   
Visual Studio Partners