I am struggling with encrypting connection strings in my Winsows Forms
application. I am using VS2005 and I am using DPAPI to encrypt my connection
strings in the config file. I am using One Touch Deploymnet to put my
application out on a network drive. The problem I am having is when a user
installs my application from the network drive, they get an error when the
application tries to decrpt the connection string. I have been reading about
DPAPI and I have found that it is either user or machine specific. Does this
mean I am using the wrong encryption method for what I am trying to
accomplish? If so, what method should I use for network installations?

Please suggest how i will host my dotnet application(frame work 2.0)
and sqlserver 2005 database using any hosting server provided by
Google.

All

I have a MonitorClient class, which will control a number of monitor classes
implementing an IMonitor interface. These monitor classes will monitor
various different things on a server. Each monitor class will have a
differently timed cycle on which to perform its probing.

My question is: which Timer class woudl it be better to use within the
monitor classes - System.Threading.Timer, or System.Timers.Timer? I've read
up on both, but cannot really see which suits my requirements better. Both
seem to use a new worker thread from the CLR thread pool on which to raise
their events, so I cannot immediately see a benefit to using one or the other
for my particular scenario.

Any advice very much appreciated.

Cheers!

I need to use the namespace defined in file1.exe in the file2.exe. So far it
worked as long as both files were in the same folder. Now I need to move one
of them. I added app.config (below) to the second file with the following
text, but it did not work. Can somebody help? Maybe there is another way to
discover file1.exe from file2.exe at runtime (file1 path is available)







1.42.6.0"
href="C:\mypath\file1.exe"/>





Note: assembly name and version are correct.

I have been asked to do a bit of research into the dotNet 3.0 framework to
try to determine when we should upgrade to this environment.
Ive done a bit of research and have read about some of the new features
(WWF, WCF, CardSpace & WPF) but I need to know if there will be any negative
impact on any of our existing systems.

Our current setup is

Client Machines
Win XP Pro SP2,
dotNet v2.0.50727
VS 2005

Server
Win 2003 R2 SP2

Where would I find a good resource for any problems that might occurr if we
upgraded.

Also, I want to have a look at new features on offer in the dotnet 3.0
framework. Can I use WWF, WCF & WPF in VS 2005? If so, where would I find
good infor & examples on this?

I've seen 2 differnt approaches people take to interfaces and am just curious
on some other opinions. For purposes of this post I am talking about adding a
new method to an existing interface. The first is that an interface can
never change, once it's "published" it is fixed in stone and if a change
needs to be made you should create a new interface that possibly inherits
from the old one. The second is that it is ok as long as the change does not
break the existing contracts, which wouldn't happen if a new method was
added, since they were not using it before they wouldn't need to be aware of
it now.

thoughts?

I have a service that starts 0->several processes to do work for the main
service. These processes are always the same xxx.exe that are generally
attached to a specific MSMQ that the process with monitor. The MSMQ queue is
passes to the process via a command line parameter.

What I need to be able to do is identify the queue that each of these
processes is monitoring from the Process information.

When the main service starts it does a Process.GetProcessByName for the
xxx.exe in an attempt to reconnect to any processes that may (still) be
running.

The problem is that I don't see any information in the Process object that
allows me to identify the queue (or anything else) that identifies this
process.

All I need is the original commandline options. But I don't see a way to get
that information either. The Arguments are in the startinfo member but are
usually not set. So is there some way to set and retrieve some type of
information to identify the process? Preferably something through the
ProcessStartInfo that can be retrieved directly through the process object.

OR is there away to snoop into the running process using reflection?

I have a class which is exposed by web services as part of different
namespace. Now I want to serialize it and deserialize object of class 'C1'
under namespace A1 to class 'C1' under namespace A2.

How can it be done?

Thanks

Hi there,

Does anyone know if there's a (simple) way to detect whether an arbitrary
"System.Type" originates from the .NET framework opposed to a user-defined
assembly. Thanks.

Hello,

Do you have an idea when VS2008 SP1 will be RTM ? I have to create a new
image of my PC and I'd like include SP1 RTM.

Regards,