Peterson's Ponderings - All Comments

re: Threading model issues when using VB 6 COM components in a .NET Web Service

Jon — Thu, 22 May 2008 13:25:43 GMT

Any developers using Visual FoxPro COM DLL's from a .Net web service will run into this same problem. But thankfully, they can implement this same workaround.

re: Threading model issues when using VB 6 COM components in a .NET Web Service

Ken Codit — Wed, 05 Mar 2008 22:00:40 GMT

I encountered the same problem attempting to use VB6 COM components WCF. The default threads created by WCF are multi-threaded apartments (MTA). The legacy code I was attempting to expose was written in VB6 single threaded apartments (STA). The following post by Scott Seely addressed the problem in a very nice way: blogs.catalystss.com/.../203.aspx

re: Threading model issues when using VB 6 COM components in a .NET Web Service

Kamran shahid — Fri, 18 Jan 2008 09:59:45 GMT

Nice article

account » Blog Archive » Performing Joins using LINQ to Objects

account » Blog Archive » Performing Joins using LINQ to Objects — Mon, 12 Nov 2007 17:32:39 GMT

PingBack from http://account.wpbloggers.com/account/?p=131

oyxa » Blog Archive » Performing Joins using LINQ to Objects

oyxa » Blog Archive » Performing Joins using LINQ to Objects — Mon, 05 Nov 2007 18:08:18 GMT

PingBack from http://oyxa.cn/?p=984

re: Customize the Default Web Service Help Page

Adam Muehlhausen — Thu, 19 Jul 2007 02:26:17 GMT

haha it would have been great to have this two weeks ago when I was working with debugging soap errors when communicating over a web service... I actually installed a packet sniffer. good stuff here though

re: A generic deserialization method

dpeterson — Tue, 17 Apr 2007 01:06:00 GMT

Good point Bryan! I wrote this method originally in .NET 2003 before generics and didn't even think about modifying it for generics when I ported it recently. For those using .NET 2.0 or above I'd recommend the generics implementation Bryan listed.

re: A generic deserialization method

Bryan Dougherty — Mon, 16 Apr 2007 18:01:31 GMT

One other thing you could do with .NET 2.0 is use generics to avoid the casting required by the callers:

string test = UtilityFunctions.SerializeToXML(cls);
SerializeMe cls2 = UtilityFunctions.DeserializeFromXML<SerializeMe>(test);

public static objectType DeserializeFromXML<objectType>(string objToDeserialize)
{
System.Xml.Serialization.XmlSerializer mySerializer = null;
XmlTextReader reader = null;

try
{
//Instantiate the Serializer with the type of object that is being deserialized.
mySerializer = new System.Xml.Serialization.XmlSerializer(typeof(objectType));
reader = new XmlTextReader(objToDeserialize, XmlNodeType.Document, null);
//Serialize the object to xml
byte[] objData = System.Text.ASCIIEncoding.ASCII.GetBytes(objToDeserialize);
object result = mySerializer.Deserialize(reader);
reader.Close();
return (objectType)result;
}
catch (Exception ex)
{
throw ex;
}
finally
{
if (reader != null) { reader.Close(); }
}

}

A generic deserialization method

Peterson's Ponderings — Sun, 15 Apr 2007 18:47:41 GMT

A while back I posted code on a method that would allow for serializing any object that was serializable...

re: SQL Server 2005 Book Recommendation

Abhang — Fri, 09 Mar 2007 19:36:18 GMT

Hi Don,
Thats how I got around that problem by modifying my code. Thanks for the information that file operations cant be included. Anyways Ill dig in this topic further if needed.

Thanks
Abhang

re: SQL Server 2005 Book Recommendation

dpeterson — Fri, 09 Mar 2007 01:51:18 GMT

Abhang,
The short answer is yes, you can include a database transaction in a distributed transaction. There are some properties off the connection objects to enlist your ADO.NET transaction into a larger distributed transaction (EnlistTransaction). Keep in mind that if you are going to use distributed transactions your application will need to interact with the MS DTC (Distributed Transaction Coordinator) so it must be running on the machine with your application.

I don't think a file create/write operation can be included in a distributed transaction. Distributed transactions usually involve committing information on more than one database provider (i.e. two different SQL Servers) or a transactional service such as MQ or other .NET assemblies. File operations though can be controlled easily enough in your normal code though using a regular database transaction. The following pseudo code is an example:

- Open a database transaction
try
- Execute unit of work in the database (i.e. call a stored proc) and use the database transaction with the connection
- Create the file
- write to the file
- Close the file
- Commit the database transaction
catch
- rollback the transaction
- delete the file
end

This pseudo code has essentially given you a transaction. If any errors occur during the database or file operations the catch event will rollback the transaction and delete the file as if the operations never occurred. If the operations are successful then the database is commited after the file operations have been completed.
- Don

re: SQL Server 2005 Book Recommendation

Abhang Rane — Tue, 06 Mar 2007 20:59:45 GMT

Hi Don,
I kinda struggled implementing distributed transactions where my front end was .NET and backend was sql server 2005. Now by distributed I do not mean just transactions related to database. I wanted to include some table operations and a file operation in a transaction. So if the table insert fails, the file operation must also be rollbacked. Is it possible in the System.Transacion namespce since it seems to have many new classes. I could put a table operation and message queue operation using System.transaction classes but not file operations.

Taking the folders out of my operating system

PM_blog — Sun, 18 Feb 2007 19:35:00 GMT

After reading a recent blog post on Lifehacker about using tagging and saved searches in Vista to simplify...

SqlServerForum.org » Blog Archive » SQL Server 2005 Integration Service Package - Configuring Connections

Tue, 06 Feb 2007 23:37:48 GMT

PingBack from http://sqlserverforum.org/archives/2007/01/28/sql-server-2005-integration-service-package-configuring-connections/

re: C# null coalescing operator

Curtis — Fri, 18 Aug 2006 14:00:18 GMT

One more reason I'm getting sick of using VB.