<?xml version="1.0" encoding="UTF-8" ?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Developer Articles</title><subtitle type="html">Giving back to the community.</subtitle><id>http://community.assistedsolutions.com/blogs/articles/atom.aspx</id><link rel="alternate" type="text/html" href="http://community.assistedsolutions.com/blogs/articles/default.aspx" /><link rel="self" type="application/atom+xml" href="http://community.assistedsolutions.com/blogs/articles/atom.aspx" /><generator uri="http://communityserver.org" version="2.0.60217.2664">Community Server</generator><updated>2007-05-25T01:50:00Z</updated><entry><title>&amp;quot;This operation requires IIS integrated pipeline mode.&amp;quot;</title><link rel="alternate" type="text/html" href="http://community.assistedsolutions.com/blogs/articles/archive/2008/02/08/3939.aspx" /><id>http://community.assistedsolutions.com/blogs/articles/archive/2008/02/08/3939.aspx</id><published>2008-02-08T17:30:00Z</published><updated>2008-02-08T17:30:00Z</updated><content type="html">&lt;P&gt;I ran into an interesting problem with .Net 3.5 today,&amp;nbsp;when trying to access response headers like so:&lt;/P&gt;&lt;FONT size=2&gt;
&lt;P&gt;context.Response.Headers.Add(&lt;/FONT&gt;&lt;FONT color=#a31515 size=2&gt;"Content-Disposition"&lt;/FONT&gt;&lt;FONT size=2&gt;, &lt;/FONT&gt;&lt;FONT color=#a31515 size=2&gt;"attachment; filename=\""&lt;/FONT&gt;&lt;FONT size=2&gt; + filename + &lt;/FONT&gt;&lt;FONT color=#a31515 size=2&gt;"\""&lt;/FONT&gt;&lt;FONT size=2&gt;);&lt;/P&gt;&lt;/FONT&gt;
&lt;P&gt;The application returns the error "&lt;STRONG&gt;This operation requires IIS integrated pipeline mode.&lt;/STRONG&gt;" Through some quick googling, I discovered that the problem existed in beta, and apparently wasn't corrected for the release. &lt;/P&gt;
&lt;P&gt;Interestingly, there is a simple workaround for adding headers:&lt;/P&gt;&lt;FONT size=2&gt;
&lt;P&gt;context.Response.AddHeader(&lt;/FONT&gt;&lt;FONT color=#a31515 size=2&gt;"Content-Disposition"&lt;/FONT&gt;&lt;FONT size=2&gt;, &lt;/FONT&gt;&lt;FONT color=#a31515 size=2&gt;"attachment; filename=\""&lt;/FONT&gt;&lt;FONT size=2&gt; + filename + &lt;/FONT&gt;&lt;FONT color=#a31515 size=2&gt;"\""&lt;/FONT&gt;&lt;FONT size=2&gt;);&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Why this simple change works I have yet to discover,&amp;nbsp;but until Microsoft gets a patch out that corrects this behavior it'll do for me.&lt;/P&gt;&lt;/FONT&gt;&lt;img src="http://community.assistedsolutions.com/aggbug.aspx?PostID=3939" width="1" height="1"&gt;</content><author><name>Joelp</name><uri>http://community.assistedsolutions.com/members/Joelp.aspx</uri></author></entry><entry><title>Flushing Network DNS Cache</title><link rel="alternate" type="text/html" href="http://community.assistedsolutions.com/blogs/articles/archive/2007/09/13/3734.aspx" /><id>http://community.assistedsolutions.com/blogs/articles/archive/2007/09/13/3734.aspx</id><published>2007-09-13T14:15:00Z</published><updated>2007-09-13T14:15:00Z</updated><content type="html">&lt;P&gt;If your domain operates on a single dns cache hosted on one of your domain controllers, you've probably encountered a situation where changing the ip address associated with a domain does not propogate to all your internal machines. In network caching, the most obvious approach ("ipconfig /flushdns") doesn't have any effect on the actual cache, and normally only time (or a hard restart) will clear the bad ips. &lt;/P&gt;
&lt;P&gt;I finally found the proper method of clearing this cache:&lt;/P&gt;
&lt;P&gt;1. On your domain controller open &lt;STRONG&gt;Administrative Tools -&amp;gt; DNS&lt;/STRONG&gt;&lt;BR&gt;2. Then right click on the name associated with your domain dns server and select "&lt;STRONG&gt;Clear cache&lt;/STRONG&gt;".&lt;/P&gt;
&lt;P&gt;That's it. All client machines depending on the network cached dns will be updated immediately.&lt;/P&gt;&lt;img src="http://community.assistedsolutions.com/aggbug.aspx?PostID=3734" width="1" height="1"&gt;</content><author><name>Joelp</name><uri>http://community.assistedsolutions.com/members/Joelp.aspx</uri></author></entry><entry><title>13 disasters for production web sites and their solutions</title><link rel="alternate" type="text/html" href="http://community.assistedsolutions.com/blogs/articles/archive/2007/08/09/3676.aspx" /><id>http://community.assistedsolutions.com/blogs/articles/archive/2007/08/09/3676.aspx</id><published>2007-08-09T19:06:00Z</published><updated>2007-08-09T19:06:00Z</updated><content type="html">&lt;P&gt;&lt;A href="http://www.codeproject.com/useritems/13disasters.asp"&gt;http://www.codeproject.com/useritems/13disasters.asp&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Greate article for addressing scalability issues in a Microsoft environment&lt;/P&gt;&lt;img src="http://community.assistedsolutions.com/aggbug.aspx?PostID=3676" width="1" height="1"&gt;</content><author><name>hunterd</name><uri>http://community.assistedsolutions.com/members/hunterd.aspx</uri></author></entry><entry><title>SSIS Packages in C#</title><link rel="alternate" type="text/html" href="http://community.assistedsolutions.com/blogs/articles/archive/2007/07/13/3640.aspx" /><id>http://community.assistedsolutions.com/blogs/articles/archive/2007/07/13/3640.aspx</id><published>2007-07-13T17:44:00Z</published><updated>2007-07-13T17:44:00Z</updated><content type="html">&lt;P&gt;In a recent project, our team needed to run a nightly import service to insert a large dataset from an access .mdb file into a SQL Server database.&amp;nbsp; The obvious solution was to use SQL Server Integration Services (SSIS) which I worried&amp;nbsp;might turn out to be some trouble,&amp;nbsp;but I was amazed to discover how simple it is to execute&amp;nbsp;an SSIS Package that&amp;nbsp;performs the import from within your code.&lt;/P&gt;
&lt;P&gt;Jeff does a good job of explaining the basics &lt;A href="http://www.codeproject.com/useritems/CallSSISFromCSharp.asp"&gt;here&lt;/A&gt;.&amp;nbsp; I would only add that you must have SSIS installed on any machine you try to run this code on or you will encounter a very unhelpful error about&amp;nbsp;"CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E}".&lt;/P&gt;
&lt;P&gt;EDIT:&lt;/P&gt;
&lt;P&gt;Another issue I encountered with executing SSIS packages from c# was in the connection permissions when trying to run the code on a different machine.&amp;nbsp;I persistantly ran into "Login failed for user '[username]'." no matter the protection level, or imported configuration file. I finally worked around the issue by using windows auth on all sql connections.&lt;/P&gt;&lt;img src="http://community.assistedsolutions.com/aggbug.aspx?PostID=3640" width="1" height="1"&gt;</content><author><name>Joelp</name><uri>http://community.assistedsolutions.com/members/Joelp.aspx</uri></author></entry><entry><title>Windows Service Installers</title><link rel="alternate" type="text/html" href="http://community.assistedsolutions.com/blogs/articles/archive/2007/05/25/3493.aspx" /><id>http://community.assistedsolutions.com/blogs/articles/archive/2007/05/25/3493.aspx</id><published>2007-05-25T05:50:00Z</published><updated>2007-05-25T05:50:00Z</updated><content type="html">&lt;P&gt;I found a good article to create an installer for windows services with some tweaking.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.microsoft.com/kb/816169"&gt;http://support.microsoft.com/kb/816169&lt;/A&gt;&lt;/P&gt;&lt;img src="http://community.assistedsolutions.com/aggbug.aspx?PostID=3493" width="1" height="1"&gt;</content><author><name>hunterd</name><uri>http://community.assistedsolutions.com/members/hunterd.aspx</uri></author></entry></feed>