Re: [ADVANCED-DOTNET] Mutex (without security) in .NET 2.0

2006-03-23 Thread Mattias Sj�gren
Matthew, > SetSecurityInfo seems to need an IntPtr You can change the handle parameter type to a SafeWaitHandle instead. Mattias === This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.

Re: [ADVANCED-DOTNET] Message Queues and acknowledgment

2006-03-23 Thread Eddie Lascu
Indeed, that is the answer JM! I was thinking to use the Journal Queue as a repository for all sent messages. However, the message is copied to the journal only when it is consumed from the queue. In other words, undelivered messages will never get to go to the Journal Queue, so even if a negative

[ADVANCED-DOTNET] Mutex (without security) in .NET 2.0

2006-03-23 Thread Matthew Wills
All, I have the below code, previously in VB.NET 1.0/2002. It is (as far as I understand) creating a mutex and then removing ACL/security information. I get a warning in VB.NET 2.0/2005 stating I should use SafeWaitHandle rather than Handle. I have read a few blogs about the benefits of Safe

Re: [ADVANCED-DOTNET] Message Queues and acknowledgment

2006-03-23 Thread J. Merrill
If you created a Message object, isn't the Id property available after Send returns? (If you pass anything other than a Message as the object to be sent, you won't be able to get the Id.) I have not tried this, but nothing else makes much sense. At 02:57 PM 3/23/2006, Eddie Lascu wrote >Hello

[ADVANCED-DOTNET] Message Queues and acknowledgment

2006-03-23 Thread Eddie Lascu
Hello everybody, I am trying to grasp the acknowledgment mechanism of Messaging namespace. I saw a bunch of examples where you can set what type of acknowledgment you want (for example positive receive and arrival where you are notified when your message reaches the destination queue and when is c

Re: [ADVANCED-DOTNET] [C#]: Multiple SQL Servers, Multiple Projects

2006-03-23 Thread Eddie Lascu
Greg, You can do that in two ways: 1. Have a configuration file for each library project and load in your main application a particular library, based on the user's role. You can store the connection strings in the lib's config file, respectively. However, be aware that you will only be able to i

Re: [ADVANCED-DOTNET] [C#]: Multiple SQL Servers, Multiple Projects

2006-03-23 Thread Gregory Miley
Eric, Yes, sorry .Net 2.0. The centralized config might do the trick. Eddie, "Leaving aside the discussion whether this is a good idea or not, this is where I lost you. Do you want to have capabilities to connect to different db instances from the same app? Or do you want to c

Re: [ADVANCED-DOTNET] [C#]: Multiple SQL Servers, Multiple Projects

2006-03-23 Thread Eddie Lascu
That capability exists in .NET 1.1 too. I used it. The difference is, I believe, that in 1.1 you can only have 2 levels of inclusion, whereas in 2.0 there is no such restriction. Anyone care to comment on this? -Original Message- From: Discussion of advanced .NET topics. [mailto:[EMAIL PRO

Re: [ADVANCED-DOTNET] [C#]: Multiple SQL Servers, Multiple Projects

2006-03-23 Thread Eddie Lascu
Hi Greg, I am not sure I understand what is your environment. I suppose you have several projects in your solution, some that generate libraries and other that generate application. I think you should have a separate "app.config" file for each application and store the connection string there. Lea

Re: [ADVANCED-DOTNET] [C#]: Multiple SQL Servers, Multiple Projects

2006-03-23 Thread Eric Means
You didn't say which version you're using, but in .Net 2.0 there's a way to include settings from another .config file (which could be a single, centralized config file), which would allow you to change a single setting in a single file and have it be picked up by any number of apps. Check out the

[ADVANCED-DOTNET] [C#]: Multiple SQL Servers, Multiple Projects

2006-03-23 Thread Gregory Miley
We are developing several in-house applications, basically one master "shell" application with several libraries. We operate on multiple MS SQL Servers: Dev, QA, Training, and Production. Each project has a Settings entry for a connection to the development server. Our goal is to have a way to modi