didn’t know this until the other day, but apparently if you are under 1.0 then all breaking change rules are off.
it really isn’t that hard to do from our end, but does feel like they should support it
yeah, they are using that in VSCode already
@ejsmith exceptionless/Exceptionless.Net#91
have you followed the troubleshooting guide in the self hosting wiki?
Please make sure you have .net 4.6.1 instaleld and you are using the elasticsearch.yml file
What are your settings in the app.config.js and web.config
Relating to rewrite rules
Here's my web.config: https://gist.github.com/Mitch528/eee2569f1d456b68136cf8cc442f7c17 and app.config.js https://gist.github.com/Mitch528/d215cb6a6cdee4f5662715c46dccdcae
I'll try reinstalling rewrite and do updates
This message was deleted
hmm that’s seems odd. let me know if installing the rewrite plugin fixes it
if you have any objections let me know :)
I noticed something with the .net client the other day and was wondering if you guys think we should fix it now before we release
if you take a look at the plugins.. the web api and mvc plugins run 100% of the time
and they set user info and do request info even if it’s already been set
so if you have an app that has both web api and mvc the web api stuff will run before mvc but will be taken out..
the issue with all of this is that we have a private info plugin that runs really early to set the user info to machine name..
then other things run and the web api plugin is towards the end that looks up the user info from the request
wondering if we need to make a service that is injected by mvc / web api for getting the user and falls back to environment.username
UserInfo GetUserIdentity(context)
IGetUserIdentity or something like that
what do you think
think it should fall back to environment.username if the interface doesn’t return anything?
with microsoft making xamarin free.. maybe it’s time we invest in a dedicated xamarin client that uses the pcl base..