<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-5879124243802807699</id><updated>2012-02-16T18:32:12.006-08:00</updated><category term='asp.net'/><category term='tech'/><category term='blogging'/><category term='scalability'/><category term='globalization'/><category term='books'/><category term='vmware'/><title type='text'>ô¿ô - Blog by Frank Rusch</title><subtitle type='html'>comments reviews notes</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://microscoping.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>frusch</name><uri>http://www.blogger.com/profile/13474037324488576363</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>15</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-2984437642032555785</id><published>2011-10-06T20:25:00.001-07:00</published><updated>2011-10-06T20:25:52.855-07:00</updated><title type='text'>Using robocopy to backup files to a D-Link DNS-321</title><summary type='text'>I use robocopy to back up my music collection to my D-Link DNS-321. I use the /xo switch so only new and modified files would be copied – like so:     robocopy c:\music\music z:\music /E /xo  However, it was taking forever because every file was considered “NEWER” than the existing backup copy. At first, I thought my music program (Media Monkey on Windows) was updating the mp3 tags or touching </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2984437642032555785'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2984437642032555785'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2011/10/using-robocopy-to-backup-files-to-d.html' title='Using robocopy to backup files to a D-Link DNS-321'/><author><name>frusch</name><uri>http://www.blogger.com/profile/13474037324488576363</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-2455450270150603933</id><published>2010-08-03T23:51:00.001-07:00</published><updated>2010-08-03T23:53:19.729-07:00</updated><title type='text'>Setting up a new Subversion repository and Trac project</title><summary type='text'>Here are the steps I use each time I need to create a new Subversion repository:  Create Repository &gt; sudo svnadmin create /var/svn/MY_PROJECT_NAMECreate TRAC project&gt; sudo trac-admin /var/www/trac/MY_PROJECT_NAME initenvDuring install, you will be prompted for the repository path created above.Set up Apache to serve TRAC project&gt; cd /etc/apache2/sites-enabled&gt; sudo nano 000-default# add each </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2455450270150603933'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2455450270150603933'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/08/setting-up-new-subversion-repository.html' title='Setting up a new Subversion repository and Trac project'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-166037874957739297</id><published>2010-06-24T17:19:00.001-07:00</published><updated>2011-10-13T10:19:47.029-07:00</updated><title type='text'>Using SQL Server to analyze IIS logs</title><summary type='text'>Rather than using LogParser to analyze IIS logs, you can import your log files in an instance of SQL Server Express.  First, create a table that has the same columns as your log file. Depending on what data you were capturing in your log files, you will need a different structure.  For example, on my Windows XP IIS 5.1 machine, I had the following fields:     CREATE TABLE [dbo].[iis_logtable_1] (</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/166037874957739297'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/166037874957739297'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/06/using-sql-server-to-analyze-iis-logs.html' title='Using SQL Server to analyze IIS logs'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-3117002327984938172</id><published>2010-06-19T12:42:00.001-07:00</published><updated>2011-03-17T22:57:24.285-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='vmware'/><title type='text'>Installing an Ubuntu 9.10 VMware image on ESXi host</title><summary type='text'>Here’s my process for creating Ubuntu VMs on and ESXi 4.0 host. I downloaded a pre-built VMware 9.10 image from thoughtpolice. I chose the amd64 version and downloaded it via bittorrent. This image won’t run out of the box on ESXi 4.0 – it must first be converted. For this, I needed to download the VMware vCenter Converter Standalone. Convert the .vmx file and deploy it to the ESXi host using </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/3117002327984938172'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/3117002327984938172'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/06/installing-ubuntu-910-vmware-image-on.html' title='Installing an Ubuntu 9.10 VMware image on ESXi host'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-4268659359291978352</id><published>2010-03-06T08:56:00.001-08:00</published><updated>2010-03-06T09:38:16.848-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='vmware'/><title type='text'>Creating a VMware 4.0 host server with ESXi</title><summary type='text'>I procured a Power Edge T105 server with the following specs:  Dual Core 4450B Processor 2x512K Cache, 2.3GHz Athlon for PowerEdge T105 8GB, DDR2, 800MHz, 4x2GB,Dual Ranked DIMMs 160GB 7.2K RPM SATA 3Gbps 3.5-in Cabled Hard Drive-Entry On board Network Adapter 16X DVD-ROM,SATA, INTERNAL   Rather than installing VMware on the (smallish) hard drive, I grabbed a 4GB thumb drive lying around to host </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/4268659359291978352'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/4268659359291978352'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/03/creating-vmware-host-server-with-esxi.html' title='Creating a VMware 4.0 host server with ESXi'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-1016526395893336218</id><published>2010-02-28T18:31:00.001-08:00</published><updated>2010-02-28T18:31:40.078-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='books'/><category scheme='http://www.blogger.com/atom/ns#' term='scalability'/><title type='text'>Scalable Internet Architectures: Static Content</title><summary type='text'>In some of my previous posts, I discussed ways to instrument static content references so their domain is configurable. This small aspect of application-level design makes it possible to offload static content delivery to a separate infrastructure from the application pages. Chapter 6 in Scalable Internet Architectures focuses on Static content, that aspect of web applications that is sometimes </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/1016526395893336218'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/1016526395893336218'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/02/scalable-internet-architectures-static.html' title='Scalable Internet Architectures: Static Content'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-7086649847103527818</id><published>2010-02-28T17:38:00.001-08:00</published><updated>2010-02-28T17:39:49.832-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='asp.net'/><title type='text'>Rewriting references to static CSS, JS, and image content, part 2</title><summary type='text'>Following up on the previous post, here are a few other options to consider:    Use a custom Expression Builder to create a include script and CSS references. This syntax &lt;%$ %&gt; would work in No-Compile pages. Use combres. I tried the demo and really liked it. It automatically renames scripts as they are updated, plus includes minification and compression. Unfortunately, I don’t think it will </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/7086649847103527818'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/7086649847103527818'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/02/rewriting-references-to-static-css-js.html' title='Rewriting references to static CSS, JS, and image content, part 2'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-4113492779441714034</id><published>2010-01-26T20:42:00.000-08:00</published><updated>2010-02-28T17:39:38.003-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='asp.net'/><title type='text'>Rewriting references to static CSS, JS, and image content</title><summary type='text'>For static content such as CSS, JavaScript, and image files, it is best practice to serve these items from a separate domain from the main content. Even if this secondary domain points to the same web farm initially, it opens up the possibility of serving the content from other servers at a later date.Other benefits:Static content domain can be cookie-free.Cache settings can be adjusted </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/4113492779441714034'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/4113492779441714034'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/01/rewriting-references-to-static-css-js.html' title='Rewriting references to static CSS, JS, and image content'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-2926120177449965911</id><published>2010-01-12T20:44:00.001-08:00</published><updated>2010-01-12T21:15:32.441-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='blogging'/><title type='text'>Blogger Backup</title><summary type='text'>May be useful for backing up blogs: http://www.codeplex.com/bloggerbackup May also consider an import to a local Wordpress instance.</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2926120177449965911'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2926120177449965911'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/01/blogger-backup.html' title='Blogger Backup'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-2876050952916144186</id><published>2010-01-12T20:34:00.001-08:00</published><updated>2010-01-12T21:15:23.652-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='asp.net'/><category scheme='http://www.blogger.com/atom/ns#' term='globalization'/><title type='text'>Review of some IResourceProvider implementations</title><summary type='text'>Problem: an ASP.NET website is connected to a CMS which permits users to modify .resx files. Modifying .resx resource files during runtime has the unfortunate consequence of causing the App Domain to reload. This can really kill your scalability since the HttpRuntime.Cache (among other things) is blown away when App Domain is reloaded. I reviewed some options for custom resource providers. First,</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2876050952916144186'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2876050952916144186'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/01/review-of-some-iresourceprovider.html' title='Review of some IResourceProvider implementations'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-2101668287249119379</id><published>2010-01-05T21:17:00.001-08:00</published><updated>2010-01-09T19:44:33.729-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='books'/><category scheme='http://www.blogger.com/atom/ns#' term='scalability'/><title type='text'>Scalable Internet Architectures, part 2</title><summary type='text'>Chapter 3 covers Mission-Critical (aka Business Critical) environments. The five “key aspects” of a Business Critical environment are:  High Availability Monitoring Handling release cycles Controlling Complexity Performance optimization Monitoring In the section on monitoring, the author mentions that SNMP (simple network management protocol) is the industry standard for monitoring of </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2101668287249119379'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2101668287249119379'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/01/scalable-internet-architectures-part-2.html' title='Scalable Internet Architectures, part 2'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-5390304499839706335</id><published>2010-01-03T22:18:00.000-08:00</published><updated>2010-01-18T19:24:55.358-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='books'/><category scheme='http://www.blogger.com/atom/ns#' term='scalability'/><title type='text'>Scalable Internet Architectures, part 1</title><summary type='text'>A few interesting points in chapter 1:The only "true" scalability is horizontal, meaning that system capacity is increased by adding more of the same hardware or software. (Scale out, not up)Scaling "vertically" is just adding horsepower (storage, CPU, etc) to an existing machine.One example where horizontal scaling is difficult is large ACID-compliant databases. The current practice to scale </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/5390304499839706335'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/5390304499839706335'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/01/scalable-internet-architectures-part-1.html' title='Scalable Internet Architectures, part 1'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-2899470823148315034</id><published>2010-01-02T15:43:00.000-08:00</published><updated>2010-01-10T11:01:49.606-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='tech'/><category scheme='http://www.blogger.com/atom/ns#' term='books'/><title type='text'>Partial tech reading list for 2010</title><summary type='text'>Here are a few books I that I need to get through. Some of these I've partially read -- I plan to do a more focused reading in the upcoming months.Microsoft .NET: Architecting Applications for the EnterpriseI've already taken a couple ideas from this book, specifically regarding UML.Code Complete, 2nd editionI've read a bit of this one already - great book that deserves its acclaim.Pro ASP.NET </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2899470823148315034'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/2899470823148315034'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/01/partial-tech-reading-list-for-2010.html' title='Partial tech reading list for 2010'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-8658748531104219377</id><published>2010-01-01T12:44:00.000-08:00</published><updated>2010-01-02T16:06:34.292-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='blogging'/><title type='text'>Some solutions for posting code in blogs</title><summary type='text'>Geshi is discussed here:
http://stackoverflow.com/questions/113440/displaying-code-in-blog-posts

A few takes on the syntaxhighlighter project, which uses JavaScript to format the code:
http://alexgorbatchev.com/wiki/SyntaxHighlighter
http://ditrans.blogspot.com/2009/03/using-syntaxhighlighter-20-on-blogger.html
http://www.hanselman.com/blog/BestCodeSyntaxHighlighterForSnippetsInYourBlog.aspx

</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/8658748531104219377'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/8658748531104219377'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/01/some-solutions-for-posting-code-in.html' title='Some solutions for posting code in blogs'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-5879124243802807699.post-8228679589635196065</id><published>2010-01-01T11:43:00.001-08:00</published><updated>2010-01-01T11:43:11.503-08:00</updated><title type='text'>New years 2010</title><summary type='text'>Happy New Year!</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/8228679589635196065'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5879124243802807699/posts/default/8228679589635196065'/><link rel='alternate' type='text/html' href='http://microscoping.blogspot.com/2010/01/new-years-2010.html' title='New years 2010'/><author><name>rusch</name><uri>http://www.blogger.com/profile/18217367659255980389</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry></feed>
