Dotnetpanel Forums

It will be nice to be able to switch website application pool from 32 bit to 64bit and vice versa through the control panel. Hope this will be added in the future.

OS: Windows Server 2008 R2

IIS: 7.5

Hello,

I'm wondering for what do you need application pool in x64?

• One is for performance on my asp.net applications
  
• The other it is for sharepoint
  

eshopverified:

It will be nice to be able to switch website application pool from 32 bit to 64bit and vice versa through the control panel. Hope this will be added in the future.

ASP.NET bitness mode setting for IIS 7 should work for your business case, shouldn't it?

 Yes. But it is a web hosting control panel. Therefore, if there was such a function, I don't have to adjust it manually.

Furthermore, current dotnetpanel will make the manual setting to default setting if a customer submit a change on the "extension" tab.

eshopverified:

Yes. But it is a web hosting control panel. Therefore, if there was such a function, I don't have to adjust it manually.

Could you please take a look at the screenshot attached? Just to make sure we're talking about the same thing... :) Thanks.

Hello,

that's default setting. Users may need to switch from 32 to 64bit and back, according to their needs. And we're currently need to do that by editing IIS AppPool configuration. That feature would be very welcome.

Take care.

Yes. I understood what you were talking about. The red circle area is default setting for account creation.

If you can also add that red circle area to the website management page under extension tab on the user level, that way, users can switch between 32bit and 64bit.

eshopverified:

Yes. I understood what you were talking about. The red circle area is default setting for account creation.

If you can also add that red circle area to the website management page under extension tab on the user level, that way, users can switch between 32bit and 64bit.

Well, we were planning to expose this setting to end-users but... UI must also maintain a balance between functionality, complexity and clarity. There is actually tons of properties of an application pool in IIS that can be customized but you must agree not all of them should be exposed on UI to provide customization for end-users.

Agreed, but this setting should be allowed to be edited by users as this is not really a heavily guarded setting such as pool memory size etc.

Dreamz:

Agreed, but this setting should be allowed to be edited by users as this is not really a heavily guarded setting such as pool memory size etc.

I would consider this as medium guarded setting because there is difference in memory usage between 32bit and 64bit application pools. If this will be provided to users then is should be also accepted by serveradmin/reseller to allow this kind of configuration change on user level.

GrZeCh:

I would consider this as medium guarded setting because there is difference in memory usage between 32bit and 64bit application pools. If this will be provided to users then is should be also accepted by serveradmin/reseller to allow this kind of configuration change on user level.

Wise idea! I'd love to develop it a step further… What if there were a possibility to expose a link on the web site properties page that allows customer to send a request to the hoster of a permanent custom tweak for the web site? Changing app pool bitness mode could be considered as such…

This question should be answered by person who need this feature. I will disable this option/link for sure because I'm perfectly happy with 32bit application pools (which is widely suggested to keep app pool in this mode).

P.S. Sharepoint websites should be managed by HostedSharepoint module since old WSS 3.0 module is no longer supported and there is new version of SP comming (Sharepoint 2010 Foundation).

In which case why bother doing the development at all if they can just submit a ticket. I believe the point was to automate this, not alert the company of the needed change (which is basically no different then a support ticket).

If you're serious about x64 deploy and hosting, you need to let people change that setting in an automated way.

The basic problem here is developer might need to change that setting a lot while he/she experiments compatibility. Sometimes you have components which cannot run in x64 mode, sometimes you just compiled for x86 and thus you cannot run x64 until you recompile. Sometimes you want to run x64.

If user / developer can change this at will, that would be a very good feature. For hoster who want to have control over this setting, it could simply become part of plan feature, the same way PHP or ASP.NET are and so it could be enabled or disabled by hoster. Once enabled for a plan, user should be able to switch by simply logging on DNP.

That would be the best way to do that. I'm mixed about ticket or message: users would already do that anyway so it doesn't sound very useful.

Take care.