10.1.0.200 Publisher Policy?

Question

My last message was about trying to get an app built on ODP.NET 9.2.0.4 to run on a machine that's only running the 10.1 client.
After doing some further research, I've discovered that publisher policies are my answer. All our machines are currently running 10.1.0.200 of ODP.NET, however, and that build did not seem to install or include publisher policies. 10.1.0.400 both includes, and installs by default these policies into the GAC.
I'm hoping there's some way I can get or build publisher policies for 10.1.0.200. That way, I could get a script run that simply installs these policies into the GAC of all machines on site. Otherwise, it seems my other option is to uninstall all the 10.1.0.200, and reinstall 10.1.0.400.
From what I've managed to learn about publisher policies, they're done by the publisher of the component. I think I need access to the .key file in order to generate my own, which of course, I do not have for the Oracle.DataAccess assemblies.
Anyone know if these publisher policies are available for 10.1.0.200 somewhere?

Answer 1

The problem does not have to do with XP/Windows 2003. It is caused by:
==========
OracleCommand cmd = new               
OracleCommand("SET TRANSACTION ISOLATION LEVEL READ COMMITTED", cnn);
cmd.ExecuteNonQuery();
==========
The COM+ transactions are defaulted to serializable. Our application reads a config file to choose the database and then issues the statement above. I know we can set the isolation attribute at the c# serviced component level at compile time. Is there a dynamic way to set the isolation at runtime? Microsofts SQL and Oracle providers do not fail with the SQL statement above.
thanks,
-Arvinder