<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>Huagati Systems Support Forum - Huagati Linq-to-SQL Profiler Support - Does the consuming project need a reference? - Messages</title>
<link>http://forum.huagati.com/messages.aspx?TopicID=86</link>
<description>Huagati Systems Support Forum - Huagati Linq-to-SQL Profiler Support - Does the consuming project need a reference? - Messages</description>
<language>en-us</language>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<generator>Jitbit AspNetForum</generator>
<pubDate>Wed, 16 Sep 2009 14:56:29 GMT</pubDate>
<lastBuildDate>Wed, 16 Sep 2009 14:56:29 GMT</lastBuildDate>
<item>
<link>http://forum.huagati.com/messages.aspx?TopicID=86</link>
<title>Message from Kristofer</title>
<description><![CDATA[By the way, I have some usage examples and background descriptions etc for the profiler in my blog:<br/><br/>1) Background + getting started:<br/><a href="http://huagati.blogspot.com/2009/06/profiling-linq-to-sql-applications.html" target="_blank" rel="nofollow">http://huagati.blogspot.com/2009/06/profiling-linq-to-sql-applications.html</a><br/><br/>2) Using the 'missing indexes' filter:<br/><a href="http://huagati.blogspot.com/2009/08/walkthrough-of-newest-filters-and.html" target="_blank" rel="nofollow">http://huagati.blogspot.com/2009/08/walkthrough-of-newest-filters-and.html</a>]]></description>
<pubDate>Wed, 16 Sep 2009 14:56:29 GMT</pubDate>
</item>
<item>
<link>http://forum.huagati.com/messages.aspx?TopicID=86</link>
<title>Message from Kristofer</title>
<description><![CDATA[Hi Mark,<br/><br/>Q1: Yes, you need to reference the logging DLL. That DLL is redistributable so you can reference it and include/distribute it with your app. It is only the log viewer that require a license to use, but the logging component is intended for redistribution together with apps, so that they can be runtime profiled in production environments etc.<br/><br/>Q2: Yes, it is a good idea to keep the logging DLL in source control or some other shared thing (just like any other referenced redistributable component), to ensure that everyone use/run the same version of the logging DLL.<br/><br/>Best regards,<br/>Kristofer]]></description>
<pubDate>Wed, 16 Sep 2009 14:54:19 GMT</pubDate>
</item>
<item>
<link>http://forum.huagati.com/messages.aspx?TopicID=86</link>
<title>Message from mkamoski</title>
<description><![CDATA[Huagati --<br/><br/>Please help.<br/><br/>I am trying to setup the Huagati Linq To Sql Profiler for the 1st time.<br/><br/>Question 1 --<br/><br/>Does the consuming project need a reference?<br/><br/>That is, referencing the sample code on the following link...<br/><br/><a href="http://www.huagati.com/L2SProfiler/runtimehelp/html/M_Huagati_LinqToSQL_Profiler_ProfilingExtensions_BeginProfiling.htm" target="_blank" rel="nofollow">http://www.huagati.com/L2SProfiler/runtimehelp/html/M_Huagati_LinqToSQL_Profiler_ProfilingExtensions_BeginProfiling.htm</a><br/><br/>...suggests the following callsite...<br/><br/>QueryProfiler qp = dc.BeginProfiling();<br/><br/>...but that callsite seems to need a reference as noted at the following link...<br/><br/><a href="http://www.huagati.com/L2SProfiler/runtimehelp/html/T_Huagati_LinqToSQL_Profiler_QueryProfiler.htm" target="_blank" rel="nofollow">http://www.huagati.com/L2SProfiler/runtimehelp/html/T_Huagati_LinqToSQL_Profiler_QueryProfiler.htm</a><br/><br/>Namespace:  Huagati.LinqToSQL.Profiler<br/><br/>...and that namespace is in the following file, I think...<br/><br/>Assembly:  HuagatiL2SProfiler (in HuagatiL2SProfiler.dll) Version: 1.15.3506.21033<br/><br/>....so I think I need a file-based reference in the consuming project pointing to the following DLL...<br/><br/>C:\Program Files\Huagati Systems Co Ltd\Huagati Linq-to-SQL Profiler\redist\HuagatiL2SProfiler.dll<br/><br/>...so is that the correct setup or is there some better way to do it?<br/><br/>Please advise.<br/><br/>Question 2 --<br/><br/>(Of course, if we license for the team, we will probably put the DLL "HuagatiL2SProfiler.dll" in our standard location for such things, which is "C:\Code\SharedReferences",  on all our development machines, and then put that DLL into source control, and then point all our projects to "C:\Code\SharedReferences\HuagatiL2SProfiler.dll" when developing to make sure everyone uses the same DLL, etc. So, this is a corollary question to Question 1, above. Is this a good way to setup our development workstations, etc?<br/><br/>Thank you.<br/><br/>-- Mark Kamoski]]></description>
<pubDate>Wed, 16 Sep 2009 14:48:31 GMT</pubDate>
</item>
</channel>
</rss>
