Hi,
I'm using ASP.NET 20082 and I can't seem to change any of the style properties of the WebCalendarView. For example, if I try to change the background color of the Footer, everything looks fine in design view, but as soon as I open the page, everything goes back to the defaults.
Any Ideas???
So here are a couple of thoughts.
The WARP panel is targeted at a non Microsoft AJAX environment. If you using VS2008 and targeting the 3.5 framework, or you have installed Microsoft's ASP.NET AJAX Extensions, you should use the Microsoft UpdatePanel instead of the WARP panel.
Although skinning is a good generic solution for styling controls, the Infragistics controls have an alternate solution called Application Styling which can be used to acheive similar results as skinning, is 100% CSS based, and comes with an external design tool - AppStylist along with 10+ pre-defined styles that you can use.
I'm not saying that you can't use Skinning, but you may want to look at Application Styling as it may do exactly what you need, with half the stress. There's a topic in the help which goes over Application Styling that I recommend you take a look at if you haven't already.
If you stick with the skin approach, in order to really understand what's going on I'd need to see a copy of your skin file and the ASPX markup you're using for the WebCalendarView.
Tony,
I agree it seems really stranges. Here's a couple of things that happen.
I am trying to apply styles using themes and .skin files. If I add a WARP control to a simple aspx page, and place a WebCalendarView, a WebScheduleInfo, and a client provider, and a button inside of it, this is what happens. (I have already created a .skin file and placed it into the appropriate theme folder and everythings wired up). On the initial request, the WebCalendarView looks like the default with no properties set. As soon as you click the button causing and async post-back, the WebCalendarView is refreshed and this time the .skin file is applied, so, a simple async post-back causes the control to change visually.
Also, if you change any of the style properties in the designer, the style will change in the design mode, but as soon as you run the page, it looks just like the default with no properties set.
I have tried this on both Vista, and Server 2003 with the same result.
So far, this has all been with StyleSheetFileName set to blank. If you set the StyleSheetFileName, then things seem to work except that the skin settings are no longer applied. (I've discovered this since my first post.) In no instance have I been able to change any style settings in the designer and get them to stick.
Randy,
That sounds strange indeed. How are you setting the style information? Are you going through CSS classes, or are you using the Style properties? Either way, it may be helpful to use IE Developer Toolbar or Firefox's Firebug to check the CSS styles being applied to a particular element.
I've also had trouble with pages being cached in the past. This is especially true if for some reason the page no longer compiles, and you're doing a "view in browser". Sometimes you'll get a stale copy of the page. Though this is a rare occurence, when it happens it can make you pull your hair out trying to figure out what's going wrong. If you kill the webserver process (aspnet_wp for IIS and webdev.webserver otherwise) it will get rid of the cache.
-Tony