Re: more on that pin:Tab problem
pinTab
<pin:Tab xxxxx ></pin:Tab> changed to pintexx.components.web.pintab.tab
BeemerBiker
04-19-2007, 9:32
Resizing the pintab control changes source code to where it does not compile. I can edit the Width and Height and change the size but anytime I attempt to resize using the mouse the source code is changed and it execute properly. Error is:
Parser Error Message: Pintexx.Components.Web.pinTab.TabItemCollection must have items of type 'Pintexx.Components.Web.pinTab.TabItem'. 'pintexx.components.web.pintab.tab' is of type 'System.Web.UI.HtmlControls.HtmlGenericControl'.
Re: <pin:Tab xxxxx ></pin:Tab> changed to pintexx.components.web.pintab.tab
Pintexx Support
04-20-2007, 8:29
Hi,
I do not completely understand what you mean.
How does your code looks like ?
Regards,
Hans-Peter
Re: <pin:Tab xxxxx ></pin:Tab> changed to pintexx.components.web.pintab.tab
BeemerBiker
04-21-2007, 12:07
This screen shot from Visual Studio 2005 show the paragraph of code that will compile properly:
http://stateson.net/pub/pintab_bugs/f1.png
I then switch from code to design and move one corner of the Pintab 2.0 box:
http://stateson.net/pub/pintab_bugs/f2.png
notice the \ arrow where I am resizing. I then switch back to code mode and the source lines have changed to this:
http://stateson.net/pub/pintab_bugs/f3.png
My program will no longer compile as the tags (??) pintexx.components.web.pintab.tab are unknown. If I replace those 6 phrases with pin:Tab then it builds correctly.
Re: <pin:Tab xxxxx ></pin:Tab> changed to pintexx.components.web.pintab.tab
Pintexx Support
04-23-2007, 9:03
Hi,
do you use .Net 1.1 or 2.0 ?
Do you use the right pinTab .Net version ?
Regards,
Hans-Peter
Re: <pin:Tab xxxxx ></pin:Tab> changed to pintexx.components.web.pintab.tab
BeemerBiker
04-24-2007, 12:52
Visual Studio 2005 with service pack 1. This is dotnet 2 and I am developing on XP Pro.
Have another problem - I keep being told this is demo but I put that pinTabKey.js at C:\Inetpub\wwwroot\pinTab\bin
is there more to it than that? The instructions for setting it up shows pinEdit but I bought pinTab.
Re: <pin:Tab xxxxx ></pin:Tab> changed to pintexx.components.web.pintab.tab
Pintexx Support
04-24-2007, 7:57
Hi,
when using ASP.Net then please set the license key to LicenseKey property of server control.
Regards,
Hans-Peter
Re: <pin:Tab xxxxx ></pin:Tab> changed to pintexx.components.web.pintab.tab
BeemerBiker
04-24-2007, 4:45
Thanks, that solved the license problem. But when I pasted the license# into the properties the phrase "pin:Tab" changed to pintexx.components.web.pintab.tab and I had to manually change it back so that it would compile. It would appear that any change in the "property page" causes the aspx source code to change. If I had typed in the phrase "LicenseKey=xxx" directly into default.aspx then it would work. This must be some interaction with VS2005 and its xhmtl 1.0 target schema??? I posted this problem to microsoft.public.dotnet.framework.aspnet but have not receive a response. Probably because it is 3rd party control.
more on that pin:Tab problem
BeemerBiker
04-24-2007, 7:26
I was able to generate this error message by attempting to copy and paste the PinTab 2.0 control onto a new page:
"This control cannot be displayed because its TagPrefix is not registered in this Web Form."
Maybe that is the problem? So how do I register it? When I first got this control I noticed it did not have an msi install script nor did it show up in the toolkit. I recall emailing techsupport or feedback and suggesting it shoulld show up in the toolkit.
So is it possible to put a PintTab control in the VS2005 toolkit so I can drag it over? I can certainly (???) copy the actual source code from "default.aspx" to my new blank page.
Re: more on that pin:Tab problem
BeemerBiker
04-24-2007, 7:30
Should spent a few more minutes thinking before posting.
There are two lines at the top of default.aspx that came from the demo program I selected to start with:
So that 2nd line does the registeration. I also see that the namespace has that Pintexx.Comp...etc that is giveing me a problem.
Is this assembly supposed to also go inth web.config? Maybe putting it into web.config with the other assemblies can fix the problem with the new page?
Is this explained anywhere like how to get started?
Re: more on that pin:Tab problem
BeemerBiker
04-24-2007, 7:32
removed html tags so it woudl print. should have prefixed this crap first.
Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="r19pintab._Default"
Register TagPrefix="pin" Namespace="Pintexx.Components.Web.pinTab" Assembly="pinTab
Re: more on that pin:Tab problem
AndrewC
04-25-2007, 4:33
BeemerBiker:
Add the PinTab .DLL file in the bin/xx folder to your Toolbox. Then you will be able to drag it onto your webform. Doing that will automatically add the TagPrefix stuff, and everything else you need to have on the page for the control to work properly.
(To add the .DLL file, right-click the Toolbox, click "Select Items...", click "Browse", and navigate to the .DLL file)
-Andrew
Re: more on that pin:Tab problem
AndrewC
04-25-2007, 4:35
Also-
Make sure you have the very latest version of the PinTab control:
http://www.pintexx.de/download/pinTabFix.zip
-Andrew
Re: more on that pin:Tab problem
BeemerBiker
04-25-2007, 4:31
Thanks - downloaded and found that pinTab.js was newer than the one I had.
Old: 2-15-2006
New: 5-03-2007
Also - VS8 toolbox has "Choose Item" not "Add Item" I do not understand why they named it that as clearly one wants to "Add" to the toolbox. If they had named it "Add Item" I would have spotted it earlier.
I am still working on why the tab prefix gets changed form "pin:Tab" to that "Pintexx.Components.Web.pinTab" which does not compile. Maybe intellisense has something to do with this renaming. I did find out how to use web.config so that the source pages dont have to have that registration code. This code seems to work:
news:132t2n9pdbv4251@corp.supernews.com
I tried pasting it here but it was not displayed in your preview panel so I left a usenet reference to it. You might want to consider enhancing your forum to allow edits and html code.