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
The issue comes up when you UPGRADE a 2008 project to 2010. New projects don't seem to be affected.
After the project is upgraded, if the old project had .NET 1.1 assemblies, it causes issues with Microsoft's parsers in that they do NOT update the designer files correctly with the appropriate namespace on objects.
Microsoft said we can't have any .NET 1.1 assemblies in the 2008 project to upgrade to 2010. So it's not specifically YOUR assembly that's the issue, it's the fact that it's a 1.1 assembly which is why I asked if you guys can provide it in a .NET 2.0 version at a minimum at this point. Thank you.
[EDIT] I forgot to attach the included ISNet assemblies in our project. Note that we do not include this assembly, but it still gets copied to the web app's Bin folder on compile.
Thanks Yudi.
This is a high priority for us as we can't get it to work at all right now. We have a grid in our application that must be editable with WebCombo integrated so it's important we get this working ASAP please. I was supposed to demo this to management tomorrow morning and right now that's not going to happen and they're not going to be happy.
Can any other users of WebUI Studio 2011, who are using Visual Studio 2008, confirm if you're having this issue too please?
Yudi,
I downloaded webuistudio2011sp1.exe from the Developer Network and just installed it on a clean system that had never had WebUI Studio installed on it and am running into the same issue.
Please note that we're still using Visual Studio 2008 due to the fact that we can't currently upgrade because of my other post due to problems in the upgrade process.
Did you do your test using VS2008?
[EDIT] After the install, I ran Update Manager was only able to update the base framework as the other available updates were locked out for whatever reason. Not sure if this is contributing to this or not but woth mentioning.
Hi Yudi,
The version I initially installed was the released version downloaded from the Developer Network. We have, since, applied the latest patches/hot fixes. Could those have updated the live samples files?
You gave me an idea though. I'm going to do a clean installation on another computer and then copy the ISNet.WebUI.Samples folder from the clean install over to my development computer as that should give me the clean copy assuming the patch/hot fix updates didn't update anything in the samples.
I went ahead and created a quick video of the issue.
[EDIT] Yudi, I just realized I didn't go further down the code in the video so you didn't see the web combo aspx code. Here it is.
164 <ISWebCombo:WebCombo ID="wcCategories" runat="server" DataMember="Categories" DataSourceID="ISDataSource1" 165 DataTextField="CategoryName" DataValueField="CategoryID" Height="20px" UseDefaultStyle="True" 166 Width="200px"> 167 </ISWebCombo:WebCombo> 168 <ISWebCombo:WebCombo ID="wcSuppliers" runat="server" DataMember="Suppliers" DataSourceID="ISDataSource1" 169 DataTextField="CompanyName" DataValueField="SupplierID" Height="20px" UseDefaultStyle="True" 170 Width="200px"> 171 </ISWebCombo:WebCombo>
This is YOUR project and samples and code so unless I have a "bad" copy it should have the same code/configuration as you or what's on the online live samples? And yes I understand the message is self explanatory. It wasn't the message I was asking about, it's the WHY.
Here's what I found from the Show Codes for the grid's definition of the two WebCombo columns:
20 <ISWebGrid:WebGridColumn Caption="SupplierID" DataMember="SupplierID" DataType="System.Int32" 21 EditType="WebComboNET" Name="SupplierID" WebComboID="wcSuppliers" Width="100px"> 22 <ValueList DataMember="Suppliers" DataTextField="CompanyName" DataValueField="SupplierID"> 23 </ValueList> 24 </ISWebGrid:WebGridColumn> 25 <ISWebGrid:WebGridColumn Caption="CategoryID" DataMember="CategoryID" DataType="System.Int32" 26 EditType="WebComboNET" Name="CategoryID" WebComboID="wcCategories" Width="100px"> 27 <ValueList DataMember="Categories" DataTextField="CategoryName" DataValueField="CategoryID"> 28 </ValueList>
The live sample does NOT have a separate WebCombo tag declared since it's embedded in the grid and the I went ahead and checked the web.config for the live samples and it does NOT have the page clientIDMode attribute/property set explicitly.
Does your local live samples code mirror what I found?
Thank you Riendy. Having the new "all" functions will be a welcome addition.
Hi Martin,
We're in the same boat as Peter, i.e., our clients use IE8 and most of our folks do as well internally and we can't force our clients or our Systems group to upgrade because of a 3rd-party bug.
Even though right now the bug above is not affecting us, that doesn't mean it won't if we wind up implementing the grid the same way Peter is doing based on new features and/or requirements so it would be essential to get this fixed and working prior to the upgrade as Peter suggests above please. Many thanks.
Our testers, so far, are confirming the fix, so very good news. Thank you for the quick response on this issue.
Martin,
As I was working on putting out a build (note that I'm filling in and do not normally do this) I noticed that the system with issues had build 430 and NOT 431. So I'll report back with how it goes once we get 431 out there. Thanks again.
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
Creating your account...