Comments (18)
Any updates at all on this would be good. We're going to be making a major move on .NET Core in a few months and Bugsnag is one of the few things holding us back at the moment.
from bugsnag-dotnet.
Any updates on the .NET Core progression? It has been available for over a year, and its meant to replace the old ASP.Net stuff.
We are moving to .NET Core / ASP.Net Core, which leaves us with only a few options if we do not have legitimate support for Bugsnag.
from bugsnag-dotnet.
I have just pushed v2 (alpha) of our .net notifier which support ASP.NET Core to Nuget. It is an alpha release right now but we would love to have any feedback on it https://www.nuget.org/packages/Bugsnag.AspNet.Core
from bugsnag-dotnet.
Hi all 👋, we have started working on this full time now. So far we have still been able to target the frameworks that I mentioned above (net35/net45/netstandard13). I will keep this thread up to date if that needs to change at any point. If you have any additional feedback or requests you can also reach me via email ([email protected]). Thanks for you patience!
from bugsnag-dotnet.
hey @jacobmarshall there are indeed plans to support .net core! We are working on a rewrite of the notifier which will target net35/net45/netstandard13, nothing to show yet but hopefully soon we can push up a work in progress PR
from bugsnag-dotnet.
This is now live everyone, thanks for all your help and feedback 🎉
from bugsnag-dotnet.
Ditto. Paying subscriber of Bugsnag and moved to .Net core on a new project that's about to go to GA. Really would like a notifier...
from bugsnag-dotnet.
I'm in need of this one as well - .net core 2.0 target for my project.
from bugsnag-dotnet.
Hi all,
We are working on this. There hasn't been much moving on bugsnag-dotnet recently, as it has taken some time for us to rethink how we need to build notifier libraries to make them easier to change in the future. I'm hoping to have something ready for the end of the year, and possibly something to try sooner.
Our next goals for .NET are:
- Having separate dlls for the different types of .NET projects
- Reducing dependencies
- Supporting report modifications through callbacks
Given these changes, we should soon be in a better position to add Core support and more. I'd like to know more about the types of apps people are building and the tools being used, and if anyone is happy to share, please reach out via this issue or via email (delisa@bugsnag). Thanks!
from bugsnag-dotnet.
Awesome, thanks @martin308, much appreciated.
from bugsnag-dotnet.
Any update on that subject?
from bugsnag-dotnet.
Any update on this, @martin308? There really doesn't appear to be much going on in this project.
from bugsnag-dotnet.
Having separate dlls for the different types of .NET projects
Isn't this what .NET Standard is supposed to take care of? This sounds backwards to me.
from bugsnag-dotnet.
@yaakov-h Agreed! But I'd like to maintain support for folks using older versions without creating issues for anyone building newer standard projects.
from bugsnag-dotnet.
Hey, Any update on .net standard support?
We are looking for a way to work with Buganag for .netstandard 1.3 SDK.
from bugsnag-dotnet.
Hi is there any help document available to implement ASPNet.Core
from bugsnag-dotnet.
@mylaimani Looks like they have examples at https://github.com/bugsnag/bugsnag-dotnet/tree/v2/examples
from bugsnag-dotnet.
@mylaimani we are working on our docs now, you can see a preview of them here https://deploy-preview-643--docs-bugsnag.netlify.com/platforms/dotnet/asp-net-core/
Note, this link will stop working once these docs changes are live
from bugsnag-dotnet.
Related Issues (20)
- WPF / WinForms for .NET Core 3 package
- Default GroupingHash?
- Incorrect handling of UnobservedTaskException
- AccessViolationException HOT 2
- Please provide way of waiting for background notification to complete HOT 1
- Use Ben.Demystifier optionally HOT 1
- Support for .NET Core 3.1 HOT 2
- No request data in the report HOT 6
- ASP.NET Core - be able to use Bugsnag in singleton services and static contexts HOT 4
- Bugsnag crashes WPF application HOT 4
- Offline Storage support for Other.NET apps and not just WPF HOT 6
- Using in Xamarin apps HOT 1
- Bugsnag is leaving running threads HOT 3
- ProjectRoots not being removed when build on Linux and hosted on Windows HOT 4
- Why called IClient? HOT 1
- Group by Exception Message and Exception Type HOT 5
- .NET 7.0 ASP.net website silently failing HOT 3
- Asp.Net Client can leak memory and trigger large number of exceptions HOT 2
- Graceful Shutdown HOT 1
- NativeAOT support HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bugsnag-dotnet.