Search Results for "visual studio .net"

...You can test your bot using the Emulator even if you haven't yet created it with Azure Bot Service or configured it to run on any channels. Before connecting your bot to the Bot Framework Emulator, you need to run your bot locally. You can use Visual Studio or Visual Studio Code to run your bot, or use the command line. When you are developing behind a corporate proxy, the Emulator will use the configured environment variables HTTP_PROXY and HTTPS_PROXY, which specify the proxy URL route for HTTP and HTTPs requests.

...Code-level material examines promises, async and await, stack traces, the event loop, native Rust add-ons, and uncaught exceptions. Tooling lessons use source maps, Chrome DevTools, Visual Studio Code, debugging modules, REPL utilities, and hot reload. Additional chapters cover New Relic, Elastic APM, ELK, Jaeger, Sentry, Telegraf, InfluxDB, Grafana, Node Clinic, and AliNode. It serves as a broad troubleshooting reference for older Node.js environments.

A complete Lua solution is written entirely in C# for the .NET, Mono, Xamarin and Unity3D platforms. Support for the complete Lua standard library with very few exceptions (mostly located on the 'debug' module) and a few extensions (in the string library, mostly). Supports dumping/loading bytecode for obfuscation and quicker parsing at runtime. An embedded JSON parser (with no dependencies) to convert between JSON and Lua tables. Easy opt-out of Lua standard library modules to sandbox what...

.Net Memory Profiler is a single C# class that builds a tree of specified object's fields, their sub-fields and so on up to primitive types. And in the "Quick Watch" window of the Visual Studio you will be able to see the memory usage by each of those fields. For more details see screenshots.

This is a debugger visualizer add-on for Microsoft Visual Studio 2005. It gives you a quick way to run a SQL statement against a database connection and view the results in a grid while debugging your code.