iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
Gentlemen,
I currently have webscheduler v3. I downloaded and installed the trial version for Webscheduler v4. I did not uninstall Webscheduler v3 prior to installing Webscheduler v4. When installing Webscheduler v4, I only selected Webscheduler v4 from the customized component list.
Question is, I am not gettting any trial messages and I think my appplication is still utilizing Webscheduler v3. How do I begin using Webscheduler v4?
Please advise and thanks -
FGary
Hi Frank,
I think by changing WebScheduler assemblies in your bin folder will change your WebScheduler version. Please ensure if you're using WebScheduler 4 assemblies in your project. Hope this helps.
Regards,Bernard
Hi Bernard,
Thanks for your quick reply, greatly appreciated.
I was able to change all my current project assemblies from webscheduler 3 to webscheduler 4. I am fairly certain I am now using the trial version of webscheduler 4 but I really have no way to know. A few questions;
1). How can I tell that I am now using webscheduler 4 and not version 3?
2). When webscheduler loads in my localhost, it does display an evaluation message, but the message appears to be for the old version as it states I am evaluating version for 2012, (see attached image).
3). I checked my web.config file and it appears that all ISNET references are still old versions as below, how do I change the references to the new versions and what would the new version syntax be?
<appSettings> <add key="ISNet.WebUI.WebScheduler.v3_0_1000.MaxJsonLength" value="2147483647" /> <add key="ISNet.WebUI.ISRes_Registered" value="true" /> <add key="ISNet.WebUI.WebScheduler.v3_0_1000.RunTimeLicenseKey" value="XX00X-XXXX-XXXXX" /> <add key="ISNet.WebUI.ISDataSource.v1_0_1500.RunTimeLicenseKey" value="XX00X-XXXX-XXXXX" /> </appSettings>
<assemblies> <add assembly="ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=B1F2A8511635667A" /> <add assembly="ISNet.ActiveReports.Exporting, Version=5.0.7200.1, Culture=neutral, PublicKeyToken=B1F2A8511635667A" /> <add assembly="ISNet, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=B1F2A8511635667A" /> <add assembly="ISNet.WebUI.ISDataSource, Version=1.0.1500.1, Culture=neutral, PublicKeyToken=C4184EF0D326354B" /></assemblies>
<httpHandlers> <add path="ISRes.axd" verb="GET" type="ISNet.WebUI.WebResourceHandler, ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=b1f2a8511635667a" validate="true" /></httpHandlers>
<handlers> <add name="IntersoftResource" path="ISRes.axd" verb="GET" preCondition="integratedMode" type="ISNet.WebUI.WebResourceHandler, ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=b1f2a8511635667a" /></handlers>
I have also attached the above web.config file settings as a text document.
Frank Gary
Hi Frank Gary,
I will answer your question point by point. Here's the answer:
1. You're using WebScheduler 4 if the assembly of WebScheduler in your bin folder was WebScheduler 4. You can see the version by opening property window of WebScheduler assemblies.
2. This message will appear if you haven't put your License Key of our control in License Manager. You could open your License manager and put the right license key for each of our control inside License manager. If you see old version product in our product in your license manager, you could delete Intersoft Solutions folder in HKEY_LOCAL_MACHINE/SOFTWARE/. This only happen in x64 machine because there are 2 registry key inside registry.
3. Simply by changing
<add key="ISNet.WebUI.WebScheduler.v3_0_1000.RunTimeLicenseKey" value="IF73T-WNYB-EQJKD" />
to
<add key="ISNet.WebUI.WebScheduler.v4_0_1000.RunTimeLicenseKey" value="XX00X-XXXX-XXXXX" />
it will change your reference of runtime license key to our WebScheduler 4 product. Please also ensure if it's the right runtime license key that you put inside your web.config.
Hope this helps.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname