Basic Date Picker Forums

Hello,

I will try to be as comprehensive as possible in this post.  The first thing I should mention is that I have already read the many responses to this issue which claims that the solution is to place the aspnet_clent folder in the "root" of the application, i.e. the same folder where default.aspx and web.config are found.

Now, on our local webserver, which is NOT localhost, the only way to get BDP Lite to work is to install the aspnet_client folder one layer ABOVE the application root, not in the root itself.  Example ...

-- This does NOT work --
[webroot]
       [aspnet_client]
       default.aspx
       web.config

-- This DOES work --
[webroot]
[asp_client]
       default.aspx
       web.config


Now, I understand that if this was only the case on our dev server, which we setup ourselves, we could have made an IIS mistake that is affecting this behavior.  However, this is also the exact same behavior we are getting on our deployment server, which is hosted and setup by a professional company (DiscountASP.net).

On the hosted deployment server, we do not have access to the layer above our account root, and we can thus not install the aspnet_client folder where we know it to work.

In our experience, hosted accounts always begin folder access at the root of the account, i.e. where the default.aspx page is found, and further applications can then be created within this root.

We have tested as many scenarios as we can, both on our dev. server and the hosted deployment server, and the only working setup is by installing the aspnet_client folder in the root of the SERVER, not the root of the application.  In most cases, this means it needs to be installed one layer above the root of the application, which on hosted servers is not usually possible.

Please advice if this is a limination of BDPLite, thus making it a non-usable control for websites hosted on third-party paid servers.

Thank you

Hi KlytusLord,

Thanks for posting your question.

This is an issue that pops up every so often for us and we really do not know exactly why/how the Virtural Root does not work on some server setups. We have tried several times to recreate this type of environment, but with no luck.

We would love to hear from anyone else out there if they have any suggestions.

BDPLite is used within 1000's of shared hosting evironments and you do not require directory access outside the Application Root.

The problem happens because the Virtual Root has not been setup properly or there is some setting within IIS that we are not aware of. It's probably related to the Virtual Directory either not being created properly or who knows what.

The issue is NOT related to BDP Lite.

The unfortunate part is that in BDP v1.1, the path to the resource files (.js, .css, images) is hard coded to point to the /aspnet_client/ directory which must be placed in the Virtual Root. The trick is the Virtual Root changes depending on whether you are browsing localhost or remote.

When deveoping locally, this is typically C:\Inetpub\wwwroot\aspnet_client\ or http://localhost/aspnet_client/.

When your application is moved to a remote server the aspnet_client directory must be uploaded to the Application Root of your project. On a remote web server the Virtual Root and Application Root should be the same. As you noted above, this is typically the same location as the default Web.config and Global.asax files. But sometimes there is a problem.

If BDPLite is not working, than the standard Microsoft Validator controls will not be working either.

Now, all that said, with the next release (v1.2) we are excited to include the new .ResourcePath property. With the ResourcePath Property the developer can specify the Directory path to the .css and image files.

The default value will continue to point to the /aspnet_client/ directory in the Virtual Root, but can be changed to point to any other location, including the Application Root, by adding a Tilde (~) or a custom location within your directory structure.

More information regarding the new ResourcePath property is available at http://forums.basicdatepicker.com/forums/284/ShowPost.aspx

With v1.2, the required JavaScript will be output inline and not linked externally.

The Beta release of v1.2 is available now. The final release should be available shortly.

Download Beta at http://forums.basicdatepicker.com/forums/505/ShowPost.aspx

So our best suggestion to fix this Virtural Path problem is to upgrade to v1.2 and set the .ResourcePath property. Adding a Tilde (~) to the start of the default string should solve the issue.

Hope this helps.

---

Thanks,
Geoffrey McGill
----------------------------------------
Coolite Inc.
Email: support [at] coolite [dot] com
Phone: +1(888)775-5888

Thank you very much for the response.  I very much look forward to getting version 1.2 - that is great news.

Right now I can not seem to download the beta, but I will check again later.

Just as some extra information, we do not have any trouble using the Microsoft validators on either our dev server or the hosted server.  I will keep doing some tests just on the off chance I can track down a pattern or setting that may help in explaining this odd glitch.

Thanks again for the reply!

Hi KlytusLord,

Sorry, there was a problem with the Download link on that post. We fixed the problem.

See http://forums.basicdatepicker.com/forums/505/ShowPost.aspx

---

Thanks,
Geoffrey McGill
----------------------------------------
Coolite Inc.
Email: support [at] coolite [dot] com
Phone: +1(888)775-5888