Hello. I am developing some classes that access SQL and Oracle databases. These classes are to be used by different applications, (windows and web applications). Thus, I need to put the database connection strings on a global location so that all applications see them (this way if I need to do changes to a connection string all applications are affected). I found that machine.config might be a proper location to do that, under the section. - Is machine.config a good solution for global connection strings? - If so, how can I access the section in my code? Thanks.

Hi. I am still having trouble with VS2005 websites and visual sourcesafe. I created a new ASP.NET website for testing in 'C:\Projects\MyWebSite' and noticed there is two different options in the SourceControl menu: - Add solution to source control and - Add web site to source control When choosing the second option the solution file is not added to source safe, just the folders and aspx files. That's fine for me. Then another developer entered source safe and 'get latest version' to his workstation. The website is copied without a solution file, so we need to create one. And this is the point where we get stuck. We create a new empty web site and point it to 'C:\Projects\MyWebSite'. But after doing this the aspx files seem like they have lost the integration with source safe. Can anyone give me a simple example on how to setup things to share a website in source safe? Thank you very much.

Thanks for the advice, but Suspend just suspends the thread infinitely. The normal behaviour of the thread should be: DoSomeWork Thread.Sleep(60000) DoSomeMoreWork But in certain occasions I need to tell the thread to execute 'DoSomeMoreWork' before the sleep ends, that is, tell it to stop sleeping and continue execution.

Hi. I have created a thread that calls Thread.Sleep(60000) after doing some work, and then it does some more work. What I wanted to do is to make the thread to resume processing and not having to wait the 60000ms until the sleep ends. For example, a function that tests if the thread is asleep, and if so, wakes it up. Is there a way to do this? I tried with the 'Resume' function, but this works only if the thread is in 'suspended' state. Thanks.

When we use 'add solution to source control' in VS2005 it automatically adds to source safe the needed files. For web applications there is just a solution file, not a project file, so if I don't add the solution file, my web application cannot be opened by other developers. Maybe there's some tricky detail.

In Visual Studio 2005 there is no project file for web applications, just solution file, so the problem must be other thing. But thanks for the advice anyway.

Hello. I am having some trouble sharing a web application with Visual SourceSafe. Here is what I've done: -I have created a web application with VisualStudio2005 and saved it to the folder 'C:\Projects\WebSite' in my workstation. -Then I added it to SourceSafe 6.0 (to '$\Projects\WebSite') with the 'add solution to source control' option in VisualStudio2005. -A developer in other workstation entered SourceSafe and clicked get latest version in '$\Projects\WebSite'. The web application was copied locally to 'C:\Projects\WebSite'. -Then he double clicked the solution file to open the project. VisualStudio returned an error message saying that the folder 'WebSite' does not existed, and then it automatically created an empty new 'WebSite' folder beneath 'C:\Projects\WebSite'. I don't understand why it searches for 'C:\Projects\WebSite\WebSite' instead of 'C:\Projects\WebSite'. I also noticed that, when opening the solution file with notepad, there is a reference to the absolute path of the solution as in the workstation where it was originally created before being added to source safe. What am I doing wrong? Any help? Thank you very much.

Hi. I have a GridView bound to a DataTable. The columns of the GridView are TemplateColumns with a TextBox in it. The textbox columns appear with the values of the DataTable. What I am trying to do is setting the TextBox to ReadOnly if certain conditions are met. I tried to do this within a handle to OnRowCreated (I get the created row in the eventargs e.Row). The problem is that I don't know how to get the TextBox object of a specific column in that row and set it's properties to ReadOnly. Any help? Thanks!

Actually that's not exactly what I wanted. The example I gave was not complete. Here's what I want to do: - Select @Res = max(Y) From table1 where X=0 - Update table1 set X=1 where Y = @Res I want to get the max record where X=0 and then update that record. The problem is that there may be two processes executing this stored procedure at the same time. Thus, they may execute the 'select' part at the same time, get the same 'max(Y)' and then update the same record. That's what I wnat to avoid. I need to assure that between the 'select' and the 'update' there is no process accessing the same record in the table. This is a concurrency problem.

Hello. I am making a stored procedure with the following SQL statement: Update Table1 set Field1='X' Where Field2 = 'N' I want the StoredProcedure to return Field3 from the updated record. Is it possible to do this? Thanks.

At this point I don't have the experience for evalutaing wether that would be a real problem or not (that's why I am puting this question here :) ), but if we suppose that everyday there is a need to add 3 or 4 additional pages to the website it seems strange to having to recompile the whole website everytime (maybe this is just a detail we are not used to when working with classic .asp pages). And what happens when 5 different people are working in the same project at the same time? Although each one is working on a different page they are accessing the same project file and compiling the same dll. Is this ok?

I am considering a commercial web application with about 100 aspx pages. If only changes in the .aspx files are needed no problem arises, since they are accessed independently and with immediate results. But if there is a need to change the code-behind file (.aspx.cs) then that file needs to be recompiled and a new dll file generated to the /bin directory (this single dll file will contain all the code-behind for all pages in the project).

Hi. May be this is a quite newby question but here it goes: - When compiling a Webforms project in VisualStudio the code-behind of all pages is compiled into the same dll file, which will reside in the /bin directory. Whenever I want to make a change in a specific page and alter it's code-behind I have to recomplile the project, which means all the pages on that project, and replace the dll file! What implications does it have, concerning project management and scalability? For a large website what is the most common used technique? Compiling all the pages in the same dll file, or divide the website in many projects, each with it's dll file? Thanks.

oh that's too bad those posts were lost. Anyway, the main question would be (just to put it in a simple direct topic): Should Enterprise Services and wrapping .NET components to COM+ be used or not? Thanks.

Hello. I've read some articles in internet concerning this subject but, as far, I haven't reached to a conclusion. The topics I would like to clarify are the following: - In classic ASP all the code is written directly in the ASP pages. If changes have to be made, only the corresponding page will be updated. In the other hand, an ASP.NET project generates a DLL file with all the code behind compiled. When a single ASP codebehind file is updated, the DLL has to be recompiled and replaced. If two persons are working in different pages in the same project they are working on the same dll file, although the changes are for different pages. Will this constitute a problem that may generate inconsistencies? When developing a website, is it advisable to sub-divide it in many projects in order to have many independent DLLs, or just one project with the whole website code in it, and thus just one DLL file? - In classic ASP the pages may access components that are registered in COM+ Component Services Manager. This ensures the support for object pooling (the reusability of component instances) and distributed transactions. In ASP.NET, apparently there isn't a direct support for these features on .NET managed components. The alternative I've found is to use .NET Enterprise Services to wrapp the managed components so that they are visible to COM+. From what I've read, the disadvantage of this solution is the overhead of the communication between managed and unmanaged environments. If there are many simultaneous connections to the website and a lot of intensity in component instance creation it may lead to bad performance. In actual enterprise scenarios what is the common layout, or what is best advisable for assuring performance (object and connection pooling) and distributed transactions in a .NET website? Thanks for your help.

Hi. Thanks very much for your advice. I will describe the steps of what I did in more detail: 1- Compiled the Dll with a strong name key file, and version set to '1.0.*' (what happens here is that the version number changes everytime I compile) 2- Copied the Dll to 'c:\Components\MyComponent.dll' 3- Registered the 'MyComponent.dll' in the GAC 4- In the Client project I added a reference to 'c:\Components\MyComponent.dll' 5- Compiled the Client project and copied it to 'c:\Programs\MyProgram.exe' (At this point all things work properly. A few days later I needed to do some changes in the Dll component) 6- I changed some lines of code in a method of the Dll project, then recompiled it (thus generating a new version number) with the same strong name key file. 7- Removed the old Dll from the GAC and deleted the file 'c:\Components\MyComponent.dll'. 8- Copied the updated Dll to 'c:\Components\MyComponent.dll' and registered it in the GAC. (Now, from this point the client program at 'c:\Programs\MyProgram.exe' stopped working, saying it doesn't find the component.) This component is to be shared between different applications, and I decided to put it in the GAC so I wouldn't have to copy it to all the applications directories everytime there is a change in the component. I expected it was enough to just update the Dll from the 'c:\Components' directory and the changes would reflect to all applications that use it. Am I missing something here?

Hello, I have a .Net executable that calls a .Net Dll, which is strong named and registered in the GAC, so it won't have to be in the same directory as the executable. I made some changes in the Dll (but didn't alter the methods headers) and recompiled it with the same StrongName Key. Then I tried to replace the old Dll with the new one, both in the Dll directory and in the GAC. But now the executable doesn't recognize the new Dll! Any help? Thanks.

Hi. Recently I had to format my system hard-drive (C:) and reinstall windows and all applications, but left my project files safe in the other drive (D:). But now I am unable to run my project. I have set my project folder in IIS, but when I try to run it from .Net VisualStudio I get the following error message: "Error when trying to run project: unable to start debugging on the webserver. The project is not configured to be debugged." also when I try to open the aspx file from a web-browser I get the following message: " Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. Source Error: Line 44: by Microsoft that offers a single logon and core profile services for member sites. Line 45: --> Line 46: Line 47: Line 48:

That method was very easy and useful. Thanks for your suggestion.

It seems that the 'doublequote' is being automatically ommited by some process. So assume it is there. =) Anyway, it doesn't work. I can't manage how to use the onclick event correctly. =( Other suggestions would be very useful. Thanks very much.