SQLServerCentral / Discuss Content Posted by David Poole / Article Discussions / Article Discussions by Author / The Enterprise Library for .NET Framework 2.0 / Latest Posts

RE: The Enterprise Library for .NET Framework 2.0

bradendavinci — Wed, 22 Apr 2009 03:00:52 GMT

thank you :)

RE: The Enterprise Library for .NET Framework 2.0

Gift Peddie — Tue, 21 Apr 2009 12:03:05 GMT

The short answer is no because I used it to develop a very large three layered application with 2005. However in 2005 you must be in SP2 or SP3 and Enterprise Library must install in your C drive or it will not run. And I think you may be running a User Instance if you are in SQL Server Express, I don't know if User Instance is supported because I was using Server instance in the developer edition.So check your service pack, Enterprise Library drive and make sure it is server instance.

RE: The Enterprise Library for .NET Framework 2.0

bradendavinci — Tue, 21 Apr 2009 11:35:57 GMT

Hi, i'm a student trying to connect enterprise Library with SQL Server 2005 but when i go to test the connection the following pops upThe user instance login flag is not supported on this version of SQL Server. The connection will be closed.Does this mean that the enterprise library doesn't support SQL server 2005?Thanks

RE: The Enterprise Library for .NET Framework 2.0

Gift Peddie — Mon, 25 Sep 2006 11:59:00 GMT

Data Access is just part of the Enterprise Application block it comes with everything you need to create a .NET application and SA is not required but DBO is needed if your application will use stored procs. This new version uses DataReader most of the time which uses sp_executesql in the background. It will help if you get to know it better. Try the links below for details and a new book is out but it was based on the older version. Hope this helps.

http://www.gotdotnet.com/codegallery/codegallery.aspx?id=295a464a-6072-4e25-94e2-91be63527327

http://msdn.microsoft.com/msdnmag/issues/06/07/PatternsAndPractices/default.aspx

RE: The Enterprise Library for .NET Framework 2.0

Steve Schwarting — Wed, 30 Aug 2006 15:44:00 GMT

We certainly haven't thrown out the idea. We will just have to investigate how best to implement it in such a manner that we are satisfied with the approach and flexibilty it gives us. Just a note, we are currently using a modified version of the precursor Microsoft Application Data Blocks. We did in fact end up "changing the code" in a # of different ways because it was lacking and we didn't like the things that it assumed. Earlier versions of it did not have the built in flexibility that the Enteriprise library appears to now have. This had me concerned that we were being herded down a path that we did not necessarily wish to go just because "everyone else is doing it". But it sound like my concerns will be allievated. Thanks for all the input.

RE: The Enterprise Library for .NET Framework 2.0

Andy Warren — Wed, 30 Aug 2006 14:44:00 GMT

Just dont throw out the idea of an enterprise library based on authentication for a couple reasons. One, if you don't like the code exactly as is, you can change it! The other is that authentication strategy doesn't really have to do with the library, but with your own coding and data access standards.

RE: The Enterprise Library for .NET Framework 2.0

Steve Schwarting — Tue, 29 Aug 2006 14:26:00 GMT

Thanks for the responses. We are still using 1.1 and an older version of the application blocks so once we move to 2.0 we will definately investigate the encryption. That might solve the trick.

RE: The Enterprise Library for .NET Framework 2.0

Tatsu — Tue, 29 Aug 2006 14:09:00 GMT

Won't it be nice when Kerberos is easier to set up. Then we can just do single sign-on and not worry about storing any credentials outside AD. If anyone knows of any good articles on how to set this up reliably I would love to know about it!

RE: The Enterprise Library for .NET Framework 2.0

Denny Rgeeh — Tue, 29 Aug 2006 13:00:00 GMT

On the contrary Steve, config files are finally the perfect place to store connection strings since the .net 2.0 framework came out with "protected configuration".This article will show you how to simplify encrypting your connection string in your config files (web AND app).http://msdn2.microsoft.com/en-us/library/dtkwfdky.aspxHope this helps ease your mind! Before this came out, I shared your opinion about the plain text.~DR

RE: The Enterprise Library for .NET Framework 2.0

Tatsu — Tue, 29 Aug 2006 09:22:00 GMT

The Data Access Application Block in the Enterprise Library makes use of the Configuration Application Block to store the connection information. The Configuration block can be used with the Cryptography block to encrypt the connection information without changing any code in the application.This article mentions encrypting the connection information: http://msdn.microsoft.com/msdnmag/issues/05/07/DataPoints/There might be a a tutorial on this on the tutorial site at http://channel9.msdn.com/wiki/default.aspx/Channel9.EnterpriseLibraryTutorials.Problem solved

RE: The Enterprise Library for .NET Framework 2.0

David.Poole — Mon, 28 Aug 2006 16:33:00 GMT

As a DBA my main concern is with apps developers who code things up with the assumption that they will have access to the SA password or similarly excessive access rights.I would have thought that if you can add your own sections to a web.config file then you should be able to implement your own web.config reader to have a connection string decrypt method. The obvious problem is that the decryption key has to be stored somewhere.

RE: The Enterprise Library for .NET Framework 2.0

Steve Schwarting — Mon, 28 Aug 2006 16:16:00 GMT

I dunno about others but I really hate it that things like Connection Strings are stored in plain text in the web.config file. What bugs me even more is that things like the enterprise library build upon that assumption and do not seem to allow for exceptions for how you might rather handle it. For instance, I at the very least want to encrypt my password but it doesn't allow for that. I haven't checked out the latest version (we are using an older version) but this still seems to be the case. The example here used a different security context so it wasn't an issue but most connections are going to require a userid and password that you want to run your queries or procs under. Does anyone have any thoughts or ideas about how best to use the enterprise library to accomplish a more secure connection string? I know no one can get at the config file from outside the company but I think someone inside a given company could easily know where to look to get at credentials for sql server given this approach. All they got to do is gain access to the machine or to source safe etc...And knowing that this is how most vb and asp applications work (even without using the enterprise library) seems to make it all the more easier for people to know where to find this info. This "rant" is more an issue for dot net forum so I apologize in advance. But I would like to hear if others have the same concern.

RE: The Enterprise Library for .NET Framework 2.0

David.Poole — Mon, 28 Aug 2006 05:28:00 GMT

My apologies for "Simplicity Stake". Guess who wrote the article late at night on using a cheap keyboard?

RE: The Enterprise Library for .NET Framework 2.0

Andy Warren — Wed, 23 Aug 2006 06:25:00 GMT

We do a very light edit on most articles, compared to a much more intense edit for articles in the SQL Server Standard Magazine. Online is a little less formal and we let the authors have some leeway around grammar and spelling!

RE: The Enterprise Library for .NET Framework 2.0

Yelena Varshal — Mon, 21 Aug 2006 12:48:00 GMT

Very Nice! Good Job!

RE: The Enterprise Library for .NET Framework 2.0

Enrique-319361 — Mon, 21 Aug 2006 10:26:00 GMT

The editor should have edited the text "For simplicity stake..." to "For simplicity's sake...".N'est-ce pas?

RE: The Enterprise Library for .NET Framework 2.0

Tatsu — Mon, 21 Aug 2006 09:00:00 GMT

If you follow Neil's advice and keep a reference to the Database object then the "slight performance hit" should only apply the first time the procedure is called. This is a little more complicating with ASP .NET apps based on the caching method but for WinForms apps it's pretty awesome.

RE: The Enterprise Library for .NET Framework 2.0

Andy Warren — Mon, 21 Aug 2006 08:18:00 GMT

I agree with your architect, the time saved is worth the minimal performance hit. Abstraction layers like these are very much worth doing. Standarding data access is a key concept and all the better if you're using something that developers coming from other companies will understand.

As much as I like abstraction, I do think it's pretty important that developers spend some time working with the raw components of ADO.Net first, then they'll both appreciate the power/simplicity of the abstraction layer and they'll be able to bypass it if/when it ties their hands too much.

RE: The Enterprise Library for .NET Framework 2.0

Neil Gibbons-248585 — Mon, 21 Aug 2006 00:44:00 GMT

Nice article!

Just a quick point.I know the author isn't from a .Net background, but a slight improvement to the code would be to use a class level variable to store the return from DatabaseFactory.CreateDatabase(). This can then be used throughout a complete "data tier" class.eg.

Public Class DataAccessLayer        Private dB As Database        Sub New()            'Instantiates the database factory class. This decouples the database            'methods from the underlying database, making it easier to change            'database types, e.g. SQL to Oracle            dB = DatabaseFactory.CreateDatabase()        End Sub        Public Function GetPreviousStatus(ByVal PurchaseOrderNumber As Long) As Integer            Dim objCommandWrapper As DBCommandWrapper = _                    dB.GetStoredProcCommandWrapper("dbo.StoredProcedure")            objCommandWrapper.AddInParameter("@Parameter", DbType.Int64, PurchaseOrderNumber)            Try                Return dB.ExecuteScalar(objCommandWrapper)            Catch exc As Exception                Throw New Exception("An Error Occured whilst querying the Database")            End Try        End FunctionEnd Class

RE: The Enterprise Library for .NET Framework 2.0

Richard R. Robson — Sun, 20 Aug 2006 08:06:00 GMT

Excellent article, easy read.

I am not a dot NET developer, but am trying mightily to come up to speed on it. I have been involved in relational databases since the days of SQL/DS on VM and DB2 V1 on MVS. This is the first I've heard of the Enterprise Library. I had been slogging through the samples. etc. in the Express sandboxes so conveniently furnished by MSFT and, while comfortable with the concepts, was getting bogged down with the detailed implementations.

I look forward to messing with this new library.

Thanks for a good read.

The Enterprise Library for .NET Framework 2.0

David.Poole — Mon, 14 Aug 2006 16:54:00 GMT

Comments posted to this topic are about the content posted at temp