← Back to all blogs


Posts in 'dotnet'

View PDF Documents in Silverlight and WPF

Studio Enterprise 2010 v3 includes the new C1PdfViewer control - the first of its kind - for viewing PDF documents in Silverlight and WPF. This viewer has its own built-in PDF parser so it has no dependency on Adobe Reader. It's considered to be experimental in this first release, because not every feature of PDF is supported out of the box (for example: special fonts and input controls are not supported yet).

What’s New in 2010 v3

Studio for Silverlight and WPF 2010 v3 has landed and we are very excited about the new features and controls found in this version. This is one of the biggest releases we've had for the Silverlight and WPF studios when it comes to significant new controls and features. For instance, we have included 3 major new controls including a report viewer, pdf viewer and a 3D surface chart control! You can't find these controls anywhere else. We also enhanced ClearStyle throughout the entire suite which makes styling our controls much easier than any other Silverlight or WPF control you'll find.

jQuery and MVC Part 2

In our last episode we went over the basics of JavaScript and the jQuery library. In this installment I will show you the basics of MVC and how it renders HTML differently than Web Forms pages, and finish up showing some basic Ajax with jQuery. When ASP.NET first arrived it was a good thing. Web Forms allowed developers to build websites in a way that was very similar to how Windows Forms applications where built, with drag and drop of controls and a "code behind" architecture. Web Forms served their purpose for many, many applications in the enterprise, and many commercial applications, both large and small were successfully built using this technology. When "Web 2.0" arrived, complete with Ajaxy interactions, Microsoft put forth their own brand of controls to handle this, and for the most part this worked, and continues to work well. However the Web Forms framework makes it difficult to build clean, lean web sites, as the technology depends on many different things in the rendered HTML to make it usable when posting back to the server. Two of the main items are ViewState and Control Rendering. ViewState is sent to the browser as a way to capture what is on the page, and what has been changed when the request is sent back to the browser. For ViewState to work, controls on the page need to be rendered with specifically named ID's. This makes it difficult to use JavaScript to find elements on the page by their ID. For example adding a button to a page that is using an ASP.NET Master Page will render the following HTML: Source code: 1: <asp:Panel ID="Panel1" runat="server">

Desert Code Camp

JavaScript delete confirmation with the C1 ASP.NET GridView

The ComponentOne ASP.NET GridView allows you to add a Delete button to remove a record from the DataTable. However there isn't a native way to add a confirmation that you really want the record deleted. It's always best to check for sure when it comes to destructive actions, so I did some spelunking and came up with a way to do it. 1. Add a Template Field column to the grid by using either the property builder, or in the declarative code of your .aspx page. 2. Go into source view and add an ItemTemplate, then an asp:ImageButton.

Silverlight Grid for Easy Data Visualization

My recorded webinar, "Silverlight Grid for Easy Data Visualization" is up on Vimeo. You can see it here, http://www.vimeo.com/16241316. And as promised I've uploaded the Slides and Code. You can get them in the attachments.

ComponentOne is Going to Space!

[update 2010-11-01] The launch was scrubbed due to high altitude winds.  We're looking for a clear weekend to try again.[/update]