Atlas RC aka Microsoft Pre-release software code named "Atlas" is available for download. It is supposed to work with VS2005 RC.
[ via Rick Strahl ]
Since it is a very common problem to make Visual Studio debug client script code, here is great whitepaper -- Word: How to Debug Script Code Using Visual Studio .NET by Microsoft. You can find here detailed explanations and screenshots. In addition all possible scenarios are summarized in this document:
- Client-side script inside .aspx pages in a web application
- Server side script (VBScript or JScript code embedded in a classic .asp or .asa
- If the page is not inside a web application
- If the page is part of a web application project
- If the page is part of a web application project created on a remote machine
- Debugging Both Script and Managed Code
Microsoft whitepaper: PDF: XQuery Implementation in a Relational Database System
"The upcoming release of Microsofts SQL Server 2005 allows storage of XML data in a new, rich data type called XML. This data type stores both rooted XML trees and XML fragments in a binary representation (binary XML). The query language on XML data type is a subset of XQuery, an emerging W3C recommendation (currently in Last Call) that includes the navigational language XPath 2.0. It is supported using the relational query processing framework with some enhancements. SQL Server 2005 also supports a data modification language on XML data type for incremental updates, which is not discussed further in this paper. This paper discusses the XQuery processing architecture in SQL Server 2005 and how XQuery expressions are compiled into query trees containing relational operators and a small number of new operators introduced for the purpose of XQuery processing. An XQuery expression is parsed and compiled into an internal structure called the XML algebra tree on which rule-based optimizations are applied. This is followed by a transformation of the XML algebra tree into the relational operator tree. This paper describes some of the interesting aspects of the implementation instead of being a comprehensive manual on the subject."
Enjoy
[ via Michael Rys ]
Hands-on Lab ASP.NET Atlas template for Visual Studio .Net Beta is ready for download. Right now I'm exploring Microsoft.Web.Atlas.dll with Reflector. Enjoy
IE weblog announced IE developer toolbar, so I downloaded it and played a little bit.
What I like:
- DOM explorer
- Outline tags
- Images report
- View cookie information
What I don't like:
- It totally messes up my Google toolbar
- It is slow
- It is not configurable
- No tooltips, poor design, etc
- Features like: "Disable", "View access keys", etc
- IE blog link ? - give me a favor, you can put it inside "About Form"
- It is not smart, I mean - not updatable, etc
- Fiddler ?
I understand it is still in beta, but you should have tested it together with other toolbars installed to start with.
Rick Strahl talks about some issues concerning Page inheritance in Asp.Net 2.0 and Visual Studio environment.
I can say in addition (from my experience with the new model) that there are many issues and problems in it. It is pretty raw right now and sure will remain such upon the release. It is pretty nice in the demos and sample projects, looks clean. But when it comes up to the serious project or some advanced asp.net stuff, you have to struggle and create workarounds to make things work :(
FrancoisTanguay just posted Event Handling Application Block to gotdotnet user samples.
"Based on the August CTP, this is a first attempt at creating a new application block. It is intended to simplify greatly how event handlers should be written by providing a policy-based mean of adding aspects or decorators to most event handlers. Exception Handling, Tracing, Weak Events, One Way events, Redirections, Cursor Handling are amongst aspects already defied. - It is entirely based on generics. - Unit tests are provided. - Easy to extend. - No documentation yet."
Enjoy (it is VS2005 format solution)
Tom Hollander talks about the upcoming changes in the future release of Data Access Application Block (DAAB) as a part of Enterprise Library for .Net Framework 2.0.
"ADO.NET 2.0 provides some important new features that have allowed us to simplify the design of the DAAB. For example, the new DbProviderFactory and its provider-specific subclasses are now used to create the commands and connections used by the block. In addition, to simplify the architecture we have eliminated DbCommandWrapper class in the previous Enterprise Library DAABs. As a result we have moved the methods that were on DbCommandWrapper have been promoted to the Database class. This should be the only breaking change from the previous Enterprise Library DAAB."
Yes, sort of ...
Atlas project went live yesterday and Scott Guthrie talks about Atlas in general:
"Our plan with Atlas is to eschew the traditional two-betas and then RTM model that we often use with big projects at Microsoft, and instead move to a model where we ship very often (at least once every month and often more frequently then that), get feedback as early as possible, share our ideas out in the open (even when they are not 100% baked), and above all use the broader developer community to make sure we build the right technology. All of the client-library code is shipped as standard .js files that you can read and look over to see what we are doing. Note that we have deliberately not removed white-space, obfuscated, or compressed them down our goal right now is to preserve developer readability (note: when compressed the entire Atlas client library is around a 32k download and cacheable on the client -- although typical scenarios will usually use only a subset of the .js files, so it will be even smaller than that). Please give us your feedback on the forums, tell us what you like and dont like, and how we can build the right product you want to use."
Another good one by Bill Pierce about Client Side Framework aka AJAX aka Asynchronous JavaScript And XML.
"With a few lines of JavaScript, we can now initiate an Asynchronous request for a web page. Asynchronous means the request is made and the user doesnt have to wait for the page to load or stare at an hourglass waiting for something to happen. The web request means we can now have seamless interoperability between client code (ala JavaScript) and server code (ASP.Net, JSP, PHP, etc). If you didnt say WOW you should at least be thinking it. With a little digging you can find a number of examples on how to use the XmlHTTPRequest object. The goal of this article is to develop a framework for using the XmlHTTPRequest object in conjunction with ASP.Net."
Lat Lays Flat - Part 1 : A Google Maps .NET Control article on www.codeproject.com by William C. Pierce.
"...As I stated above, my main goal for this control was to make it easy to use a Google Map using .NET languages. I also tried very hard not to use any fancy or proprietary "hacks" or workarounds when creating this control."
Excellent. Including source files and help files.
Rick Strahl posts an article on How Asp.Net works or "A low-level Look at the ASP.NET Architecture".
"With ASP.NET you can perform tasks that previously were the domain of ISAPI extensions and filters on IIS with some limitations, but its a lot closer than say ASP was. ISAPI is a low level Win32 style API that had a very meager interface and was very difficult to work for sophisticated applications. Since ISAPI is very low level it also is very fast, but fairly unmanageable for application level development. So, ISAPI has been mainly relegated for some time to providing bridge interfaces to other application or platforms. But ISAPI isnt dead by any means. In fact, ASP.NET on Microsoft platforms interfaces with IIS through an ISAPI extension that hosts .NET and through it the ASP.NET runtime. ISAPI provides the core interface from the Web Server and ASP.NET uses the unmanaged ISAPI code to retrieve input and send output back to the client. The content that ISAPI provides is available via common objects like HttpRequest and HttpResponse that expose the unmanaged data as managed objects with a nice and accessible interface."
znichter nails it.
"The GUID is a wide column (16 bytes to be specific) and contains a unique combination of 33 uppercase and numeric characters. This column because it is the primary key is going to be stored in, of course, the clustered index (unless specified to be a non-clustered index), and will be the page pointer for each leaf page in a non-clustered index. Also, if a GUID is used instead of an integer identity column then the 33 characters need to be matched for each row that is returned using that column in the where clause. If a high volume of inserts are done on these tables then GUID's being large will contribute to page splits, as will the fact that NEWID() generates a random value, which could place a new record on any of the data pages will cause performance problems."
My 2 cents. Don't use GUID as PK if you don't need to because:
- table row size limit in MSSQL
- storage + memory. Imagine you have tables with 10000000 rows and growing
- T-SQL operators available for INT like >, <, =, etc
- GUID is not optimized for ORDER BY/GROUP BY queries
