Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Contents tagged with Automation

  • browserstack

    If you are doing web development, then you have the headache of testing your web application on various browsers. What makes it even more “fun” is the fact that on a given OS you might run multiple browsers of various versions. What I have done in the past was targeting “standard” browsers. That was long time ago, and today reality is a little more challenging. Along with the desktop browsers, nowadays there are mobile browsers that are making things a bit more complex.

  • cURL to Scrape Data

    I ran into a situation today when one of our microsites that was developed by a 3rd party is no longer… manageable. To be less politically correct, we don’t have access to the data anymore. Nothing significant, but annoying. The only way to see the data was through the web site. Yet data was paged, with about 40 pages. This is where curl was really helpful. Apparently, you can parameterize URLs (thanks to Sameer’s post) passed into the command, as well as the output. Here’s an example:

  • Automate or Not

    When system is built, no one wants to baby sit after its up and running. Therefore, there is a strong desire to automate everything, including error handling. But sometimes automation is not suitable for every error, and here is a good example.

  • PowerGUI

    In my last post I have described the move from NAnt to PSake that is based on PowerShell. One missing piece for making the whole experience smooth was Visual Studio support for PowerShell syntax and some Intellisense. Gladly, I have run into PowerGUIVsx, that does just that: syntax highlighting, intellisense, and even debugging. Sweet!