Nightly news, 1 Mar 2013

LightSpeed

  • Suppress code gen of LINQ IQueryable for transient entities
  • Fix issue for C# templates with association fields being marked private when derived types are present, should be protected in these cases
  • Fix for issue with delete cascading of an entity where it was associated with the base entity in a CTI relationship

Web Workbench

  • Fix for an issue with invalid warnings being emitted regarding missing folders on save
  • Updated CoffeeScript to 1.5
  • Added support for Literate CoffeeScript
  • Added an option to suppress warnings about missing folders to Web Workbench options
  • Updated the Visual Studio Gallery

WPF Diagrams

  • Resolved a connection point placement issue caused by deserializing a rotated node.
    (details)

WPF Elements

  • Resolved a DataGrid auto column size bug.
    (details)
  • Resolved a bug caused by using Snoop to debug the DataGrid.
    (details)
  • Resolved a bug calculating the extent of the DataGrid.
    (details)
  • Resolved an edge case issue in a DataGrid with 1 column and FrozenColumnCount = 1.
    (details)
  • Resolved an exception when dragging the DataGrid padding column header.
    (details)
  • Added Minor and MajorRangeButtonsVisibility properties to the TimeExplorer.
    (details)
  • Resolved a DataGridPager bug.
    (details)
  • Resolved a bug in LineAreaSeriesBase.GetY when the data includes null points.
    (details)

As usual the free editions of the nightly builds are available right now from the downloads page, and the full editions from the store.

Java, JavaScript and Ruby providers for Raygun.io

Raygun.io - exceptional error tracking

This week I’m pleased to announce a range of new error reporting providers for Raygun.io — to compliment our existing .NET, WinRT, NancyFX and PHP providers. We now also have providers for Java, JavaScript, ColdFusion and a community contributed Ruby provider.

JavaScript provider

The JavaScript provider integrates into web apps and reports on errors that occur on the client side of your web application. These errors are typically hidden from you, the developer, because you have no visibility of them from the server. The downside is that they can majorly damage the user experience of your application given the rise of JavaScript use in recent years.

The JavaScript provider is ready for you to use but is just a start. JavaScript error reporting support in browsers is, how do we say this nicely, “pretty average”, but we do as reasonable job of reporting what we can. This includes the URL, the message and if the browser supports it, a stack trace. We have plans to improve upon this further with time and appreciate your feedback on the provider as it stands now.

Read more about reporting JavaScript errors to Raygun.io here.

Java provider

Callum on our team has been busy working on adding support for Java applications. We’ve got specific support for Servlets, JSP’s and standard exception reporting. We’ve also had good community response on adding additional support to other parts of Java.

Read more about reporting Java errors to Raygun.io here.

Ruby provider

We have fairly substantial plans for a Ruby provider for Raygun. Justin McNally (github, twitter), an all round nice guy and not affiliated with us at all, couldn’t wait and dived in and wrote a nice light weight provider for Ruby. His contribution can be found on GitHub over here. He’s been using it in his organisation successfully. We’ll be working with Justin to include his efforts with our own and are happy to support folks working with the Ruby provider.

Read more about Justin’s Ruby error provider for Raygun.io here.

ColdFusion provider

Another all round good guy, Kai Koenig (github, twitter), has developed a provider for ColdFusion. He’s put the provider up on GitHub and has offered to maintain that provider. If you’re a ColdFusion developer he’s happy for you to submit things on Github.

Read more about reporting ColdFusion errors to Raygun.io here.

The REST API for submitting an error

We’ve recently published the first cut of our public API for reporting exceptions. This lets you build your own providers for other platforms. We’ve even had people writing specific providers for applications, like Alex Henderson building a plugin for the very cool Enterprise Tester software testing product.

You can read more about the REST API here.

Thanks!

We love that the community has rallied behind Raygun in the month since we launched. We have plans for more providers (Python is not far away!) and can’t wait to see the cool things you produce. Let us know at hello@raygun.io as it would be great to profile your creations.

If you haven’t added Raygun.io error tracking to your app yet, you can get your free trial here.

Happy coding!

Tagged as Raygun.io

How using Raygun.io makes Windows Store submission a breeze

Sample Explorer with Raygun

As a lot of you will know, we’ve made 2 exciting releases recently: Raygun.io and Metro Elements.

Raygun.io is our error tracking service that you can integrate into your apps using a few lines of code. When exceptions occur in your app, the details are sent to the Raygun.io service which you can view in the convenient dashboard. The dashboard groups the exceptions together so that you can easily see the unique exceptions that are being raised. It also has a smart email notification system. You’ll get enough emails to know what’s going on with your apps, but not so much that it clutters your inbox. Raygun.io has providers for ASP.NET, PHP, WPF and WinRT plus many more currently under development.

Metro Elements is our suite of controls for WinRT app development. Metro Elements includes a sample explorer app that shows off all the controls in action. This app has been published on the Windows Store which is what I’ll be talking about today.

Make Windows Store submission easier with Raygun.io

In the Metro Elements Sample Explorer, I integrated Raygun.io so we can track and fix exceptions if they occur. Doing this ended up having a helpful consequence we hadn’t though of: While submitting the sample explorer app to the store, the Microsoft testers managed to crash the application in a scenario we had overlooked. This exception got instantly logged into the Raygun.io dashboard for the Sample Explorer. Using the stack trace and the type of exception, I was able to reproduce and solve the bug in a few minutes. Half an hour later, the Microsoft testers had finished looking through the app and I got an email saying that it failed because the application crashed. No problem – as Raygun.io already helped me resolve the issue, I simply submitted the updated package again which later passed certification and was published on the Windows Store.

Not only did Raygun.io help save time by sending an error report before the certification even failed, but the way Raygun.io presents the exception data is far easier to interpret than the error dump that you get in the failed certification report. Are you submitting an app the Windows Store? Get Raygun.io – it’s a no-brainer.

If you’re a WinRT app developer, you can check out the free Metro Elements Sample Explorer from here. More information about the actual control suite is found on the website.

We’d love to hear about your experiences with Raygun.io, let us know by writing a comment on this blog.

Announcing Raygun.io: handle your app errors better!

Raygun.io - exceptional error tracking

I’m very excited to announce the general availability of Raygun.io – the best way to record, track and manage errors in your applications!

Raygun is a cloud service that records all your software errors, including a lot of information to help with diagnosing the problems. Let’s dive in and see if Raygun could be right for you.

Do any of these ring a bell?

  • I don’t log any exceptions but I know I should.
  • I log exceptions to a file but I only look at them when somebody complains.
  • I email myself every exception but, honestly, I mostly ignore them now as many are junk.
  • Alex gets the error emails but he’s on holiday this week.
  • I’m pretty sure Jim was being emailed errors but he left the company three months ago.

How will Raygun make your job easier?

  • You get a beautiful dashboard showing the overall health and trends in your software
  • We group similar errors so you’re only working with unique errors
  • We don’t email on every error – only on new sightings, re-occurrence rate changes and threshold changes. Simply put, a manageable number of notifications that you can absolutely turn off if you’d rather check the site only.
  • Raygun records a lot of data about every error. This makes resolving errors easier than ever.
  • Permanently ignore junk exceptions (like those caused by spam bots or broken web crawlers) so you never see or hear from them again
  • Simple workflow for resolving, ignoring or permanently ignoring an error group.

These features have been designed to help reduce notification overload and reduce your time to resolve an error.

Raygun.io gives instant insight into app health from the dashboard

Raygun is great for teams too!

All Raygun accounts, from the smallest to the largest, can have an unlimited number of users associated with it.

Raygun also supports multiple applications per account so you can easily track every moving part of your software easily.

Supported Platforms

At present we have support for .NET, WinRT, NancyFX and PHP. You integrate a small component into your software and set an API key and you’re good to go!

Support for Ruby, JavaScript, Objective-C, Java and Cold Fusion is coming soon and already under development. If you’d like to get early access to these providers email us at hello@raygun.io.

A rock solid choice

Application errors can be costing you time and money due to lost sales. We have a team dedicated to the development of Raygun and are already processing millions of application errors every day. Whatever the size of your application and needs we can support you.

Be up and running in the next 10 minutes!

Setting up Raygun doesn’t take long at all. Standard integration time is measured in minutes and you can be logging errors quickly.

All accounts include 30 days free trial of our largest plan so you can see how much better zapping errors can be!

Sign up to raygun for a free trial

Tagged as Products, Raygun.io

Nightly news, 8 Feb 2013

LightSpeed

  • Add constructor which allows user to specify the list of stop words used by the Lucene analyzer

Web Workbench

  • Intelliense for Less mixins is now correctly triggered when in a CSS property context

WPF Diagrams

  • Added DiagramConnectionPointBase.HasConnections property
    (details)
  • The drag-panning user operation now respects the AllowInfiniteScroll property.
    (details)
  • Resolved a diagram scrolling bug.
    (details)
  • Resolved a critical selection bug.
    (details)

WPF Elements

  • Resolved a rendering bug in the DataGrid caused by changing the visibility while a custom cell has focus.
    (details)
  • Added DataGrid.AutoColumnWidthBehavior property.
    (details)
  • Resolved a minor charting selection bug.
    (details)
  • Added Chart.CanToggleSelection property.
    (details)
  • Added Chart.CanDeselectOnClickNothing property.
    (details)
  • Added Chart.IsRightClickSelectionEnabled property.
    (details)
  • Resolved a DataGrid auto column width issue.
    (details)
  • Added DataGridColumn.MaxAutoWidth property.
    (details)
  • Added DataGrid.CanAutoSizeColumnHeaders property.
    (details)
  • DataPoint selection logic now respects the IsRightClickSelectionEnabled and CanToggleSelection properties.
    (details)

As usual the free editions of the nightly builds are available right now from the downloads page, and the full editions from the store.

Tagged as General

Archives

Join our mailer

You should join our newsletter! Sent monthly:

Back to Top