Emmanuel's Screencasts

How do you manage passwords on multiple web sites?  Do you always use the same password?  Or if you have different passwords, how do you make sure they are strong passwords and how do you store them securely? 

How many times in a week do you have to remember web credentials?
Watch the screencast below to better manage your Web Passwords

In this screencast, Emmanuel shows you a few ways to manage your Web passwords, including a tip on how you can remember just one password (your “master password”), which is used to generate unique, complex passwords for the Web sites you visit.  It’s safe, secure and very easy to use.

This is part 1 of 2 screencasts I recorded that show how to speed up Windows Azure Development (see part 2 here).   Specifically, in this screencast I create a sample Windows Azure project with one web role - but the web role is smart enough to load its settings when running the Azure fabric or not - allowing it to be hosted in IIS.

For more articles, screencasts and tips check out www.ehuna.org – you can also follow me on twitter.com/ehuna

Here’s what is covered in the video:

1. To get this working you need Microsoft Visual Studio and the Windows Azure SDK (November 2009 CTP) – you can get it here at -
  http://www.microsoft.com/windowsazure/windowsazure/
2. Create a new CloudService project (VB.Net) called “AzureSpeed1”, with an ASP.NET web role called “AzureSpeed1_WebRole”. 
3. Create a setting in the ServiceConfiguration.cscfg file.
4. Running the project in the Windows Azure local development fabric.  Benefits of running in a virtual machine.  A bit slower since we’re running in a virtual machine. 
5. Displaying a setting in the default.aspx page – web role still running in the local development fabric.
6. How I’m impatient – I’m used to years of RAD – Rapid Application Development with IIS, ASP.NET, VB.NET and Visual Studio.
7. You can run your web roles in the local development fabric – but you can also run them in IIS!  Make sure handle settings and logging properly.
8. Add new IIS site, match azure local development fabric and IIS ports (change by one number – e.g. 8080 and 9080).  Try loading the page and see the exception.
9. Knowing whether you’re running the Azure fabric or not.
10. Smarter function to read settings – if not running in the cloud from the web.config.
11. We’re back to RAD development!  Build your web role (really just an ASP.NET site) and start testing your ASPX pages – no need to run the local development fabric.
12. Conclusion: whenever you implement a feature in your Windows Azure projects, make sure you add support for running both in the Windows Azure fabric (local development fabric or Staging/Production cloud) or on-premise hosted in IIS.  Settings, logging, and ASP.NET sessions are examples of features that need to support both.

Below you can find sample code and additional tips related to this screencast.

This is part 2 of screencasts I recorded that show how to speed up Windows Azure Development (see part 1 here). Specifically, in this screencast I show how we can create a macro in Visual Studio 2008 to attach or debugger to an IIS process.

We can then also create a keyboard shortcut for fast debugging of an Azure web role running in IIS. For more articles, screencasts and tips check out ehuna.org - follow me on twitter.com/ehuna

How to speed up Windows Azure Development (Part 2 of 2) from Emmanuel Huna on Vimeo.

Here’s what is covered in the video:

1. The rinetd trick and the RinetdService – accessing your windows azure web roles from the real IP (not 127.0.0.1). See “An easier way to access the Windows Azure local development fabric from another computer” -
  http://blog.ehuna.org/2009/10/an_easier_way_to_access_the_wi.html
2. Adding a breakpoint in Visual Studio 2008.
3. W3WP.EXE – the IIS host process.
4. Tools > Attach to process – takes forever for the list of processes to come up.
5. Attach to W3WP.exe the IIS host process.
6. Load the ASPX page in the browser and debug your code-behind.
7. Create a Visual Studio macro (Macros > Record Temporary Macro).
8. Rename and save the temporary macro.  Right-click and run.
9. Visual Studio > Options > Keyboard > Create keyboard shortcut.
10.  Change something in your code, right-click web role and build, press “CTRL+SHIFT+ALT+?” and open a browser to access your ASPX page.  Boom!  Debug your code in 1-2 seconds!
11. Attach to process when running a windows service or a worker role.
12. If using the ASP.NET custom session provider that uses Azure storage, don’t use it in development.  Set your web role instance count to 1 and store your ASP.NET sessions in proc.

Good Times!
Below you can find sample code and additional tips related to this screencast.