Today's news about Visual Studio 2005.
Microsoft has made a series of changes to the Visual Studio 2005 tool set that will be shipping in November this year..
Read More
ASP.NET v2.0 has a couple new ways to reference connection strings stored in the web.config or machine.config file.
A typical web.config file in v2.0 could have the following section which is placed directly under the root <configuration> section.
<
connectionStrings>
<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"/>
<add name="MainConnStr" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|main.mdf;User Instance=true" providerName="System.Data.SqlClient"/>
</connectionStrings> You can reference this directly from code using:
[C#]
string connStr = ConfigurationManager.ConnectionStrings["MainConnStr"].ConnectionString;
[VB]
Dim connStr As String = ConfigurationManager.ConnectionStrings("MainConnStr").ConnectionString
Note that the namespace for this is System.Configuration so for a console application the full namespace is required.
Or you can reference this declaratively within the ConnectionString property of a SqlDataSource:
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
ConnectionString="<%$ ConnectionStrings:MainConnStr %>"
SelectCommand="SELECT [au_id], [au_lname], [au_fname], [state] FROM [authors]" />
[via owscott]
Now Google has stepped into Instant Messaging service. Yes, Google Talk has come!
I saw a thread having information about the new messenger from Google..I just got an invitation so thought of posting it here for others..
http://www.google.com/talk/index.html
Richard Turner and Ingo Rammer have joined forces to publish two papers that show the relative performance of Web Services, .NET Remoting, Enterprise Services, and MSMQ using more realistic, business centric services. While not meant to be a benchmark, the articles do attempt to further clarify the best uses of each technology.
The first article deals with the comparative performance of Web Services, .NET Remoting, and Enterprise Services. Tests involve creating and storing orders into the Northwind database, retrieving data from the same database both as a Dataset and as custom business objects, and retrieving just a single client's information.
The second article covers the performance characteristics of the System.Messaging (MSMQ) namespace as compared to using the COM+ MSMQ interface. The tests for this article include queueing and dequeueing messages containing empty, small, and larger data objects as well as a comparison of the serialization techniques available.
This article is very interesting and informative:
http://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnwebsrv/html/asmxremotesperf.asp