This helps Umbraco development by adding realtime Log information. In the future other utilities will be added.
This allows you to view realtime logs of your Umbraco ASP.NET CMS website, directly in the Chrome Developer Tools. A requirement of having an Umbraco site 7.5 is needed for this to work along with the package installed in the Umbraco site to allow it to communicate with the Chrome extension. You can install the following Nuget package to make your website https://www.nuget.org/packages/Umbraco.DevTools.Logger/
- (2016-07-25) Pawel Breś: REALLY useful during developing Umbraco projects!
- (2016-08-12, v:1.0.0 beta) Extguru 9: Partnership Offer
Hello! I represent the company EXT.GURU. I have reviewed your extension, and I would like to invite you to work with our company. I have analyzed, that your extension "Umbraco Developer Tools" can bring you a guaranteed high income. You can get the maximum profit with our automatic service for monetizing browser extensions, while our advertising is not annoying or malicious, and does not prevent the extension of functionality. Our system optimizes traffic from around the world. We provide coordination of all the nuances and suggestions of webmasters. Payments are carried out upon request during one hour at a convenient system to you. We would also like to note that our system does not interfere with other systems of monetization, you can plug in our program as an additional method to generate an income. If you have any other extensions, we can discuss. We look forward to collaborating. Sincerely EXT.GURU team. Contacts ICQ: 654784658 Jabber: [email protected] Skype: extguru [email protected] email: [email protected]
- (2016-08-02, v:1.0.0 beta) Jan Vanuytrecht: Error Cannot connect to signalr log4net hub
Hi, This plugin doesn't work for any site that we have set up (local machine & on other machines). Error: Error: Cannot connect to SignalR Log4Net Hub or you do not have permission to. We use Log4net config specified in our web.config instead of the log4net.config file in the config folder. Maybe that's the issue for this plugin? Or can we check some settings in the log4net config to get this up and running? Tnx for your help in advance!