Huagati Systems Support Forum :: Forum

	9/16/2009 2:48:31 PM permalink
mkamoski Posts 43	Huagati -- Please help. I am trying to setup the Huagati Linq To Sql Profiler for the 1st time. Question 1 -- Does the consuming project need a reference? That is, referencing the sample code on the following link... http://www.huagati.com/L2SProfiler/runtimehelp/html/M_Huagati_LinqToSQL_Profiler_ProfilingExtensions_BeginProfiling.htm ...suggests the following callsite... QueryProfiler qp = dc.BeginProfiling(); ...but that callsite seems to need a reference as noted at the following link... http://www.huagati.com/L2SProfiler/runtimehelp/html/T_Huagati_LinqToSQL_Profiler_QueryProfiler.htm Namespace: Huagati.LinqToSQL.Profiler ...and that namespace is in the following file, I think... Assembly: HuagatiL2SProfiler (in HuagatiL2SProfiler.dll) Version: 1.15.3506.21033 ....so I think I need a file-based reference in the consuming project pointing to the following DLL... C:\Program Files\Huagati Systems Co Ltd\Huagati Linq-to-SQL Profiler\redist\HuagatiL2SProfiler.dll ...so is that the correct setup or is there some better way to do it? Please advise. Question 2 -- (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? Thank you. -- Mark Kamoski
	9/16/2009 2:54:19 PM permalink
Kristofer Posts 240	Hi Mark, 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. 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. Best regards, Kristofer
	9/16/2009 2:56:29 PM permalink
Kristofer Posts 240	By the way, I have some usage examples and background descriptions etc for the profiler in my blog: 1) Background + getting started: http://huagati.blogspot.com/2009/06/profiling-linq-to-sql-applications.html 2) Using the 'missing indexes' filter: http://huagati.blogspot.com/2009/08/walkthrough-of-newest-filters-and.html
pages: 1

|