Exceptionless.NET 3.2 Release Notes

Exceptionless LogoThe .NET Exceptionless client has received several improvements and some bug fixes in version 3.2. Details below!

A special shout-out to @airwareic, @srijken, @xbelt, and @mgnslndh for contributing and helping make this release happen. You guys rock!

Please download and update to the latest source here, and you can view the full change log here.

.NET Exceptionless Client v3.2.0 Release Details #

Additions & Improvements #

Read Configuration
We added support for reading configuration from environmental variables and app settings

**Closing Applications
** Closing applications after submission is now easier due to the new SubmittedEvent event handler.

**Custom Persistence Settings
** The new QueueMaxAttempts and QueueMaxAge configuration settings allow custom persistence settings and are intended to improve offline support. Thanks @airwareic!

Data Exclusions Improvements
We've made huge improvements to Data Exclusions, which now check default data and extra exception properties.

**New Overloads
** Thanks @xbelt for creating overloads for CreateLog and SubmitLog to accept the LogLevel enum!

Custom Themes
@mgnslndh updated the styling of the CrashReportDialog to play nice with custom themes. Thanks!

**Dependencies
** All dependencies (Nancy, NLog, etc) have been updated.

**Deprecated!
** The EnableSSL property has been marked Obsolete because it is no longer used. ServerURL is now being looked at for this.

Fixes #

**Startup()
** Startup() was overriding configured dependencies - Fixed!

**Empty Errors
** We fixed a bug where you could have empty errors submitted with no stack trace info.

API Keys

  • Previously set valid API keys were being overwritten with default API keys, so we fixed it.
  • We also fixed an issue where ApiKey couldn't be changed after the client was initialized.

Reference IDs
An issue with submitting generated reference IDs was resolved, thanks to @srijken

**Updating WebAPI Package
** @srijken also fixed another issue where updating the WebApi package would remove the Exceptionless Module. Thanks again!

NLog
Nlog wasn't working with .NET 4.0. This has been resolved.

IsolatedStorage
There was a problem that caused IsolatedStorage to not be able to be used. Fixed!

Min Log Level
NLog and log4net have been updated to allow setting the min log level.

What Say You? #

As always, we're listening to your feedback, comments, suggestions, and rants!

Exceptionless 3.1 Released! If You Thought It was Fast Before...

exceptionles-3-1-headerIf you thought Exceptionless was fast before, prepare to have your mind blown by what we've been able to do in version 3.1, which released today.

In short, we've reduced cpu and memory usage, increase caching efficiency, and sped up searching, all quite significantly as you'll see below.

Along with these speed boosts, we've also made Job improvements (look for a blog post on this soon) and upgraded to .NET 4.6 (self-hosters, please install .NET 4.6 on your servers before upgrading).

Details on the release changes can be found below.

It's All About Speed! #

CPU & Memory #

We reduced the CPU and Memory load across the entire app. This allows the application to use fewer resources, meaning it has more time to process additional events, making everything faster. Between making Exceptionless and Foundatio 100% Async and these improvements, we've drastically increased the efficiency of the entire platform.

Below, we see the increase in performance from two examples. On the left, we see a reduction in CPU and Memory usage for a deployed web app instance. On the right is a visible reduction in CPU usage for an Elasticsearch node.

cpu-memory-percentage-improvements

Elasticsearch Queries #

By profiling the Elasticsearch queries for efficiency and usage, we've been able to reduce the overall number we were running and improve the efficiency on the ones that still are.

search-request-rate-improvements

Caching #

Caching efficiency has been improved by removing redundant components that were utilizing valuable resources. For example, we removed the SignalR Redis Backplane, which drastically decreased the number of calls to Redis. Overall, we've made the app smarter throughout regarding how we cache and retrieve data.

cache-improvements-2

Caching-improvements

Long-running API Tasks #

We've offloaded long-running API tasks to background jobs, freeing up a lot of resources in the app and allowing us to scale work items independently. For example, marking a stack as fixed or removing a project may take a few moments to be updated now, but the trade-off is worth it. We're working on updating the UI experience to prompt users that the task is running in the background.

Other Improvements #

Jobs #

We've made each Job a console app, so it's much easier to debug and deploy. Look for a full blog post on Job improvements soon.

.NET 4.6 #

Exceptionless is now running on .NET 4.6, which has improved startup time due to various improvements with the new version. Self-hosting users should be sure to upgrade to .NET 4.6 on their servers before updating Exceptionless.

Upgrading #

For full release notes and to download the latest version, please visit the GitHub Release Page.

Always Improving #

We're always striving to improve the efficiency of Exceptionless and all of our projects. If you see any room for improvement or have any comments when using anything from us, please send us an in-app message, submit a GitHub issue or contact us on the website.

Exceptionless JavaScript Client V1.1.0 Release

Exceptionless JavaScript ClientWe've been hard at work on several things here at Exceptionless, including a minor version release of our JavaScript Client!

Please see the details of this release below.

Also, we would like to give a shout out to @frankerbersoll, @srijken and the entire community for help squashing bugs, reporting issues, and providing general feedback. You guys rock.

Exceptionless JavaScript Client V1.1.0 Release Notes #

You can view the full change log for a list of all changes in this release.

You can also Download Exceptionless JavaScript Client V1.1.0 on the official release page.

Introducing Foundatio 3.0! Now with Async & Increased Efficiency

Foundatio 3.0Foundatio is a pluggable, scalable, painless, open source solution for caching, queues, locks, messaging, jobs, file storage, and metrics in your app.

In Version 3.0, we've made several improvements, including, as promised in our initial Foundatio blog post, going full async.

Take a closer look at the new enhancements, below, and head over to the GitHub repo to try Foundatio today. We think you'll find it very handy.

For all our current users, you'll need to upgrade your Foundatio NuGet package and existing Foundatio code to use the async implementations/conventions. The update should be fairly straightforward - we haven't had or heard of any issues so far, including when upgrading Exceptionless.

What's New in Foundatio 3.0 #

API Changes #

We've gone 100% async, which means no more blocking synchronous code, allowing your apps to be even more responsive. For more on async and its benefits, take a look at this Microsoft article.

Along with going completely async, we've removed non async methods from the API and simplified the API overall. We wanted to make it easy for developers to roll out new implementations and use the existing API.

New methods

We also added new, useful methods across all the APIs to make it easier to perform common tasks. One example includes adding CalculateProgress() to WorkItemHandlerJobs. We hope these helpers allow you to be more productive.

Efficiency Improvements #

Because we always want more speed out of our apps (and we know you do, too), we used Red Gate's ANTS Performance Profiler to profile various apps, such as Exceptionless, and track down "hot" sections of code. By hot, we mean those pieces of code devoured more resources and took longer to run than all other application code. By doing so, we were able to pinpoint core pieces of Foundatio that were performing poorly compared to what they could be doing. Then we fixed them.

A few optimization examples
  • Maintenance code in various locations like queues, caches, etc, could and would run in a tight loop, sometimes pegging the CPU to 100% depending on the configuration. By running through and removing that maintenance code, or changing the way it was implemented to be triggered only when needed, rather than running in a constant worker loop, we drastically reduced CPU load and increased efficiency.
  • We also made massive improvements to queues and locks, on top of the maintenance code changes. Our Dequeue and AcquireLock methods would constantly pull for new items in a loop with a small timeout, which is obviously inefficient. Now we are using async monitors and pulse when a message is received over the message bus. This allows for huge improvements as the code will wait/sleep for a single monitor (of multiple monitors that could be waiting) to get triggered. This means your app isn’t wasting CPU cycles waiting, or external network calls looking for locks or new queue items. Instead, it’s running your app code and getting immediately notified when the lock is available or a new queue item is enqueued. Pretty slick!
  • Caching got a huge performance boost, too. For InMemoryCache clients, we moved from reflection-based object copying to using Expression Trees. This reduced the time required to get items from cache by a large percentage. Read more about implementing Expression Trees and see the difference it makes here.

Check It Out - Feedback Appreciated! #

We made many other improvements to ensure your apps run fast when using Foundatio, too many to be listed here. If you're already using it, just update your NuGet package to the latest version to take advantage of these improvements. If you're not using it yet, try it out. It's worth a shot, we promise!

Once you've given it a go, please let us know what you like, or what you hate, by posting a issue on Foundatio's GitHub Repo.

Until next time, happy coding!

Find Software Bugs with the Exceptionless JavaScript Client in Minutes

Exceptionless JavaScript Client
If you missed our JavaScript Client announcement, this is a great chance to see just how quick and easy the client is to install and use! You can be finding those hard to track down bugs, errors, and exceptions, as well as tracking other events and log messages, in literally minutes.

We've made it super easy to get up and running, as you'll see below. Take a look and let us know what you think!

Report & Log Errors & Events in 1:37 #

The Text Version #

A simple step-by-step guide to getting the Exceptionless JavaScript Client demo up and running on your local machine.

The only pre-requisite is an Exceptionless account, or you can host the entire platform yourselfOpen source, baby!

  1. Download and extract the Exceptionless JavaScript Client from GitHub
  2. Log in to your Exceptionless Dashboard and get your project's API key (Admin > Projects > Select Project > API Keys)
    * If you don't have a project, you'll need to create one by going to Admin > Projects > Add New Project
  3. Open the extracted folder on your local machine and go to the "example" folder, then edit index.html.
  4. Replace the API key in the exceptionless.js script tag with your own, and comment out the line with serverURL in it (not needed for demo).
  5. Open index.html in your browser and open your browser's developer tools console so we can see the events fire.
    * We've added quick-fire buttons to this page that automatically generate events for you to play around with for the purpose of this demo.
  6. Click on one, generate 100 random events for instance, and you'll see the events queue up in the console. After a few seconds, you should see a queue processing notification telling you it's done processing.
  7. Go back to your Exceptionless project dashboard, and you will see the events hit the system in real time.
    * Make sure you are viewing the appropriate project and time period in your dashboard, otherwise you might not see the new events come in.

It's That Easy! #

As you can see, the JavaScript client is super easy, super fast, and super flexible, for use in almost any project you might have.

We hope you'll give it a shot, and we also hope you'll let us know what you think by contacting us via an in-app message, submitting an issue on GitHub, or through the website.

Here's to becoming Exceptionless!

Squash Bugs Faster & Speed Up Development with Exceptionless

Developer Bug Tracking

Calling All Developers!

**Stop** beating your head against the keyboard tracking down those hard-to-find bugs and cut down your development time in general by using Exceptionless to **report and log errors, feature usages, and any other event** within your project.

We're not just for .NET developers anymore. Our JavaScript client allows you to use Exceptionless in almost **any development environment**, and you can get it up and running in minutes!

Learn more below, including how to get started in **just about a minute and a half**!

Now Serving...
**5,000,000+ Events Per Month
2000+ Active Projects**

"Exceptionless is awesome. I've STOPPED worrying about whether I'm losing customers to bugs I don't know about." - Eric B.

Up & Running In Minutes #

This 1:37 video demonstrates how quick and easy it is to get the Exceptionless JavaScript client up and running. Take a few minutes to integrate it with your project and gain visibility you've never had before on bugs, feature usages, and more!

IT'S. THAT. EASY. #

"Exceptionless allows us to prioritize fixes smarter by showing frequently occurring errors. In real time!" - Ryan H.

The only thing you need to get started is a free Exceptionless account, or you can even host it yourself! Once you have that, you can user the JavaScript or .NET client to get started pushing events to your new dashboard.

Then you'll be on your way to becoming... Exceptionless.

User Spotlight, Plus Fun Stats - Thank You to All of Our Awesome Users!

Exceptionless Growth StatisticsThis month (Aug, '15) we will surpass 5 MILLION EVENTS PER MONTH!

That's pretty huge, so we thought we would celebrate by highlighting a few of the awesome companies that use Exceptionless and throw out a some pretty cool statistics we dug up from the database.

If your company isn't on this list, don't worry - it's not because we don't love you! If you would like your company highlighted on the website, simply send us an in-app message explaining how Exceptionless has helped you squash bugs and improve your development.

Fun Stats #

  • Nearly 2000 ACTIVE projects
  • More than 1350 ACTIVE organizations
  • Right at 100 new organizations and 140 new users per month!
  • 800,000 new events each month, month over month - 4,600,000 total in July!

A Few of Our Awesome Users/Companies #

User Report #

userreport_logo_cmykUser Report is an online survey and feedback tool used to collect information about and from website visitors. The data User Report's tools identifies is useful in usability studies, helps websites better identify their demographics, gives users an easy way to provide feedback, and more. The company's solutions are used by ebay, Toyota, National Geographic, and other large national and international brands.

Visit the User Report website to learn more.

eMarketer #

eMarketerLogo-blackUsed by Facebook, MasterCard, and other large worldwide brands, eMarketer provides insights into the digital marketing world by providing customers with the information they need to run their business effectively and efficiently online. This information includes industry-specific research, insights, and benchmarks.

"Exceptionless allows us to prioritize fixes smarter by showing frequently occurring errors. In real time!" - Ryan Hoffman, eMarketer

Actipro Software #

PageHeaderCompanyLogoActipro Software provides industry-leading .NET user interface controls for a variety of frameworks, including WPF, WinRT, Silverlight, and WinForms. They are known for their syntax-highlighting code editor control, SyntaxEditor, among other things.

.NET developers should definitely check out Actipro Software.

Beth Israel Deaconess Medical Center - Harvard Medical School Teaching Hospital #

BIDMC is one of the nation's preeminent academic medical centers focusing on excellence in clinical care, research, and education.

header_logo

"The primary reasons that we switched to Exceptionless from our own code is that Exceptionless captures additional detail (including code line numbers), Exceptionless has a better interface and design for reviewing and managing errors and bugs (including summary views that we didn’t previously have), and we no longer need to maintain our own error-logging code." - Philip Dickerson, BIDMC

LegalDesk #

legaldesk.logoLegalDesk is software designed for managing law firms or independent legal practices and includes everything from document organization and sharing to timesheets and finances/billing.

Check out LegalDesk's Website (Italian)

CodeSmith Tools #

codesmith-tools-largeCodeSmith Tools is a Dallas-based software development company focused on creating software tools that increase developer productivity. Their flagship product, CodeSmith Generator, has seen huge success over the years as a template driven source code generator that automates common application source code creation for text-based languages. They also provide a variety of frameworks for generating proven architectures.

Learn more about CodeSmith Generator or CodeSmith's other Frameworks.

IKA #

imagesXIKA is a laboratory equipment maker in the research and development field that builds innovative magnetic stirrers, mixers, overhead stirrers, shakers, homogenizers, mills, rotary evaporators, calorimeters, laboratory reactors and the specially developed software for analysis applications.

"I’m using Exceptionless to report bugs /crashes which I encounter routinely while testing the UI. It helps me zero in on what could be the issue, AND have a documented track of what all errors I’ve seen... I’d say that Exceptionless helps me find all the bugs which I’d have to spend more time on zeroing in on, faster." - Bharat Mallapur, IKA

Want to learn more, visit IKA.in.

Teamaton #

logo-tagline-teamatonTeamaton is a small software development company focused on creating user-friendly and profitable web applications for its clients using .NET technologies.

Right now, Teamaton is working on an intuitive time tracking tool where they have implemented Exceptionless to monitor errors during development.

Learn more at Teamaton.com.

The Agileist #

the-agileistThe Agileist is a development company based in Kansas City that specializes in Azure web development, systems development, and systems integration in an agile environment.

TheAgileist.com

Thanks Again! #

Once again, we'd like to extend our thanks to all the awesome users we have that make Exceptionless such a great project to work on and use. Everyone has provided excellent feedback, allowing us to continue pushing towards a faster, more efficient, more effective solution for all your error and event reporting needs.

Self Hosting Exceptionless - Free and Fast!

Self Hosting Exceptionless

Self hosting allows you to run your own instance of Exceptionless, our real-time error, feature, and log reporting tool, on your own systems - FOR FREE!

Not Just Free, but Fast! #

When developing Exceptionless 3.0, we put extensive focus on making self hosting much easier, and therefore more viable, for our users.

It is now possible to get a test environment up and running on your local machine in only a few minutes, and production environments can be set up very quickly as well.

Or continue reading for more information and a demonstration.

How Easy? Super Easy! #

Demo Time! #

Getting your self hosted instance of Exceptionless up and running is super easy. In the video below, Blake does the entire install on his local machine and is sending events to Exceptionless in less than 2 minutes!

Please note that you should review the requirements on the Self Hosting Documentation page before installing your own instance.

We're Always Improving #

Exceptionless has come a long way, and it's only going to get easier, faster, and more robust moving forward. Our users are a huge part of that, so please submit an issue on GitHub or send us an in-app message if you have any feedbacks, bugs, installation questions, etc. Thanks!

Exceptionless V3.0 - Changes to the Build Process, Dependencies, and Self Hosting

version-3-featuredVersion 2.0 was a pretty big rewrite for us, and we're happy with how everything played out, but that doesn't mean we're done!

We've been working on 3.0, and it's ready.

What was the focus, you ask? To make life easier for you! We've simplified the build process, removed dependencies, and drastically improved the ease of self hosting.

Check out the details, below, and upgrade today!

Removed Dependencies #

Previously, MongoDB was a major dependency that increase the complexity of the overall project. All the data previously hosted in MongoDB is now hosted in ElasticSearch, making it super easy for users to self host or develop Exceptionless since you only need to set up ElasticSearch (which you had to do anyway).

With this, Redis is no longer configured by default, but you can set it up easily by setting the connection string. We definitely recommend using it.

Removal of the MongoDB dependency brings us one step closer to running Exceptionless on vNext, on any operating system. We hope to achieve this soon, but do not have a timeline.

Easier Self Hosting #

The goal is to make self hosting as easy as possible so anyone can set it up and try Exceptionless out.

With Exceptionless 3.0, we now have a single build artifact that contains bo the SPA app and the API end server, with default configuration. The ZIP file contains a batch file you can run to download and start ElasticSearch, launch IIS Express with a temp website, and load your browser automatically with the Exceptionless test instance. This lets you load up everything and play around with Exceptionless in a single click!

Another change to the configuration is that you now have the ability to set every Exceptionless API Setting via Environmental Variables.

Check out the documentation for detailed Self Hosting Configuration docs.

Simplified Build Process #

In order to make it easier and faster to deploy, we removed the OctopusDeploy build dependency and are now using Azure Git deploy, which pulls directly from a GitHub repository that contains the build artifacts.

With this move, our mindset changed regarding the master branch. For us it means production, but for you it means that whatever is in our master branch is stable and currently deployed to live. We no longer have to wait for a build to complete, create a production release in OctopusDeploy, then manually deploy it, we just commit to git and the rest is history!

Expect more on this topic from us soon. In the mean time, enjoy the simplified build process.

Upgrading to 3.0 #

The only users that need to worry about upgrading anything for this new release are self hosters. If you are self hosting Exceptionless, please review the Self Hosting Documentation, which contains information about upgrading your existing install.

So What? #

Well, what all this means for you is that we will be able to update things much quicker, and that life just got way easier for all you self hosters out there!

Let us know what else we can do to make life easier for you.

Introducing Foundatio - Pluggable Foundation Blocks for Building Distributed Apps

Exceptionless Foundatio App Building BlocksIn the process of developing Exceptionless, we realized there was a lack of good, simple, open source solutions for caching, queues, locks, messaging, jobs, file storage, and metrics when building scaleable applications.

We tried an open source Redis cache client for caching, but it went commercial (expensive) and there wasn't any in-memory implementations. For the message bus, we looked at NServiceBus (good product, high cost, not open source friendly) and MassTransit (local setup a pain, Azure support lacking), but were left disappointed. For storage, we simply could not find a solution that was decoupled and supported in memory, file storage, or Azure Blog Storage.

So, naturally, we built our own!

Meet Foundatio - your key to painless, scalable development and testing for your app! Let's take a look at some examples, below.

Using Foundatio #

To start using Foundatio for your project, simply get the appropriate package from NuGet.

Below are small examples of what is possible with Foundatio caching, queues, locks, messaging, jobs, file storage, and metrics. We hope you find these explanations and samples useful, but please let us know if you have any questions or comments.

Caching #

Foundatio provides four cache implementations, all derived from the ICacheClient interface, that save you expensive operations when creating or getting data by allowing you to store and access the data super fast.

These implementations include InMemoryCacheClient, HybridCacheClient, RedisCacheClient, and RedisHybridCacheClient. Learn more about each in the Foundatio Readme Caching section.

For Exceptionless, we use RedisHybridCacheClient to cache users, organizations, and projects, which has a huge performance boost since we don't have to serialize the item if it's in local memory cache.

Foundatio Caching Sample
using Foundatio.Caching;

ICacheClient cache = new InMemoryCacheClient();
cache.Set("test", 1);
var value = cache.Get<int>("test");

Queues #

Foundatio includes three queue implementations, each derived from the IQueue interface, for First In, First Out (FIFO) message delivery. These include InMemoryQueue, RedisQueue, and ServiceBusQueue. Read more in the queues section of the readme.

We use queues, along with Foundatio Storage (below) to queue events for Exceptionless. Using both allows us to keep payloads small and limit system load.

Foundatio Queue Example
using Foundatio.Queues;

IQueue queue = new InMemoryQueue();

queue.Enqueue(new SimpleWorkItem {
Data = "Hello"
});

var workItem = queue.Dequeue(TimeSpan.Zero);

Locks #

To ensure any resource is only accessed by one consumer at any one time, use one of the two Foundatio Locks implementations, each derived from the ILockProvider interface. These implementations include CacheLockProvider and ThrottlingLockProvider. These providers take an ICacheClient, ensuring code locks across machines. Read more on the repo.

We use locks to only run single instances of jobs (below), and more.

Foundatio Locks Sample
using Foundatio.Lock;

ILockProvider locker = new CacheLockProvider(new InMemoryCacheClient());

using (locker) {
locker.ReleaseLock("test");

using (locker.AcquireLock("test", acquireTimeout: TimeSpan.FromSeconds(1))) {
// ...
}
}

Messaging #

Derived from the IMessageBus interface, our three message bus implementations let you publish and subscribe to messages within your application. Use the InMemoryMessageBus, RedisMessageBus,or ServiceBusMessageBus implementations based on your needs. Read more about each implementation on GitHub.

Exceptionless utilizes the message bus extensively to pass messages such as events being created, stacks being changed, etc, throughout the system.

Foundatio Messaging Example
using Foundatio.Messaging;

IMessageBus messageBus = new InMemoryMessageBus();

using (messageBus) {
messageBus.Subscribe<SimpleMessageA>(msg => {
// Got message
});

messageBus.Publish(new SimpleMessageA {
Data = "Hello"
});
}

Jobs #

Run jobs by calling Run() or passing it to the JobRunner class, which allows you to easily run jobs as Azure Web Jobs. All jobs are required to derive from the JobBase class.

Around here, we use the jobs feature for processing events, sending mail messages, and more. Some jobs, such as our DailySummaryJob, which we only want to run once, also use locks (above) to only run one instance.

Foundatio Jobs Sample
using Foundatio.Jobs;

public class HelloWorldJob : JobBase {
public int RunCount { get; set; }

protected override Task<JobResult> RunInternalAsync(CancellationToken token) {
RunCount++;

return Task.FromResult(JobResult.Success);
}
}

var job = new HelloWorldJob();
job.Run(); // job.RunCount = 1;
job.RunContinuous(iterationLimit: 2); // job.RunCount = 3;
job.RunContinuous(token: new CancellationTokenSource(TimeSpan.FromMilliseconds(10)).Token); // job.RunCount > 10;

Job.exe -t "MyLib.HelloWorldJob,MyLib"

File Storage #

Derived from the IFileStorage interface, we offer three file storage implementations, including InMemoryFileStorage, FolderFileStorage, and AzureFileStorage. Read more on each in the ReadMe. Using all IFileStorage implementations as singletons is recommended.

File storage is used by Exceptionless in conjunction with queues (above), among other things.

Foundatio File Storage Example
using Foundatio.Storage;

IFileStorage storage = new InMemoryFileStorage();
storage.SaveFile("test.txt", "test");
string content = storage.GetFileContents("test.txt")

Metrics #

Our three metric implementations derive from the IMetricsClient interface and include InMemoryMetricsClient, StatsDMetricsClient, and MetricsNETClient. Get the details on the repo. Note that these implementations should be used as singletons.

Metrics are used throughout the Exceptionless system to provide insight into how the system is working and get external alerts if events are not processing or report how much load is on the current system.

Foundatio Metrics Sample
metrics.Counter("c1");
metrics.Gauge("g1", 2.534);
metrics.Timer("t1", 50788);

Development #

If you would like to contribute to Foundatio, clone the repo and open the Foundatio.sln Visual Studio solution file to get started. Let us know if you have any questions or need any assistance.

The Future of Foundatio #

As with any development project, Foundatio is a work in progress and we will continue developing it, however it is extremely stable and used in production by various companies, including Exceptionless (obviously). The next major steps are full Async support (some implementations already have it), and vnext support.

Naturally, we want to know what you think and what we should work on next, so please let us know!