Find out how unemployment is affected. You would hate to take 3 weeks pay and have to turn down 6 months of insurance because you quit instead of got laid off - unless you get a better job right away. I don't know what your local laws are like, but you better find out. Don't ask HR either, they have lied to me about this before! No matter what you do start looking for a new job now. My expirence has been a few months latter they close the plant, so no matter what you shouldn't count on that job. Call all your contacts. Ask everyone you work with if they will be a reference. (here is one time you can openly do it and not get into trouble, use it!) In fact get those references down first! The rest is between you, your family, your savings, and your next job.

Hi, Thanks for your information. Yes, the designer is in the same assembly as the control it is designing. This assembly is seperate to the assembly containing the designer host, but as the designer host can 'see' the control, I'm sure it must have access to the designer as well. Both assemblies have full trust (they will only be used on intranet, and security protocols are already in use in other parts of the app, so it's not really a security risk). I have now resolved this problem. I used Reflector to see what TypeDescriptor.CreateDesigner(IComponent comp, Type designerBaseType) was doing, and copied the code to a local method so I could debug it. If you are interested, the problem appeared to be that Type.GetType(designerBaseType) was returning null. (the designerBaseType parameter was hard-coded to IDesigner). I got around this problem by changing all the controls (no, users will never add their own controls to this designer!) to use the constructor of the DesignerAttribute that accepts two parameters, and set the second one to the same type as the first. When the component is then added to the design form, I get the DesignerAttribute for that type, and call TypeDescriptor.CreateDesigner with the type specified in the second parameter of the attribute. OMG :omg: I don't really understand what I just wrote! :) - it you are really interested, feel free to email me and I'll try to explain in more detail!!! Thanks for your reply. Simon. PS: Is Reflector the most AMAZING tool for .NET development?!?!

No, I thought I had tried that, but obviously not because it now works!! Thanks very much for your help - most appreciated! Cheers.

The way I would try to do it is by making a templated control along with a designer class for the control. If you have access to Kothari and Datye's book, "Developing ASP.NET Server Controls and Components", they have an example of a templated control starting on page 321 and later make a designer class for this control on page 386. hth, Orange

Simon_uk wrote: If anyone cares, then this is still a problem in the 1.1 framework so you have to deal with Euro's manually. I care very much, what is the exact problem? Some sort of bug or... I'm about to port (re-write actually) a 400,000+ lines of code c++ program to c# that will definitely be parsing user entry of Euro values (not to mention pesos, kroners etc etc).

I hope I understand what you want correctly - If you have the appropriate properties, you can use data binding to your session data to dictate behaviour at runtime. For example, I needed to store a "tag" with a text box over post-backs, so I derived a class from TextBox (which is derived from WebControl), added a property like so in the .vb: <Bindable(True), Category("Appearance"), DefaultValue("")> Property [Tag]() As String Get Return Viewstate.Item("tag") End Get Set(ByVal Value As String) Viewstate.Item("tag") = Value End Set End Property and in the aspx, I can databind that property like so: <cc1:mytextbox tag='<%# DataBinding code here %>' runat="server"> When you render the control, you can use the information in the property to dictate what it looks like. YMMV, HTH -- Ian Darling

What's that in real money? ;) David Wulff Build: 1 succeeded, 0 failed, 0 skipped

Hi I don't really think I know enough to write an article to be honest. Also, I'm not very good at explaining stuff in a concise fashion! :) Feel free to ask me any questions or use any of my code in the article though (and I'll rate it a 5 for ya! ;) ). Cheers, Simon.

Yeah, thats a good point. I forgot it was protected. :( Thanks for the info about casting the current http handler to a Page though - didn't realize I could do that. Unfortunately deriving from Control isn't an option at this stage. :( Thanks again, Simon.