October 2007 - Posts
Most of us have been testing the Visual Studio 2008 Beta 2 VPC images.
Microsoft has announced that the current Visual Studio 2008 Beta 2 VPC images will expire on November 1, 2007, rather than March 15, 2008 as originally announced.
It is strongly encouraged that you take all necessary steps before November 1, 2007 to back up all your projects and move your Team Foundation Server data to an alternate location. For instructions on moving your TFS data please refer to the article Moving Team Foundation Server,
For the latest information and up to date information on this please refer to the Visual Studio Developer Center.
A short Frequently Asked Questions (FAQ) is listed below:
Q. Will my data be available after November 1, 2007?
A. This is still being researched, however, currently the understanding is that customers will NOT be able to access their date after November 1st unless the data is moved to an alternate installation location.
Q. Can I reset my system date to re-enable the OS image?
A. Again there is still research being done, however, from the current understanding of the problem resetting the system date back DOES NOT re-enable the OS image.
If I have any further information to share will be sure to let you know.
In this third article of the series I'll show how you can change the Page Flow Application Block of the Web Client Software Factory to have a current definition and current page flow.
In this second article of the series I'll show how you can change the Page Flow Application Block of the Web Client Software Factory to get page flows by its definition name instead of its definition type.
Filed under: .NET, Architecture, ASP.NET, Community, SoftDev, Microsoft, MSDN, MVP, Web, WCSF, PnP, SoftwareFactories, PageFlow
With IIS7 a new transfer method is available in the HttpServerUtility class. It's the TransferRequest method.
What this method is intended to do is behave like the HttpResponse.Redirect method without the penalty of traveling to the client and back.
I said "is intended to behave" because it still doesn't, like Luís Abreu found out in his first attempt to use this new method. Fortunately, Thomas Marquardt already knows about it and said they will fix it.
This problem that Luís ran into reminds us that there is still too much going on when you call TransferRequest that won't be if a Page Module is used. So, I guess they are still useful.
Filed under: .NET, Architecture, ASP.NET, Community, SoftDev, C#, Microsoft, MSDN, MVP, Web, PageModules, IIS
In this first article of the series I'll show how you can use the Page Flow Application Block of the Web Client Software Factory without a database.
Filed under: .NET, Architecture, ASP.NET, Community, SoftDev, Microsoft, MSDN, MVP, Web, WCSF, PnP, SoftwareFactories, PageFlow
I'm starting a series of articles where I'll show how (in my opinion, obviously) to the Page Flow Application Block of the Web Client Software Factory could be improved.
Filed under: .NET, Architecture, ASP.NET, Community, SoftDev, Microsoft, MSDN, MVP, Web, WCSF, PnP, SoftwareFactories, PageFlow
I usually just share these news through my shared readings feed, but this one is too big the let it pass without saying anything.
Glenn Block just pointed me to his post on this.
Jeffrey Palermo also has a great post about the new MVP Framework For ASP.NET.
I'll wait to see what's coming out of that. I like extensibility, dependency injection, inversion of control all that good stuff that's missing from ASP.NET (adding a few providers doesn't make ASP.NET a framework with extensibility, dependency injection, inversion of control, etc.).
The fact that both the "new" and the "old" model can live together in the same web application means that nothing has been done to make better ASP.NET web applications. It's just another way to glue some pages together.
What I would like to see is, for example:
- Pluggable authentication providers
- Pluggable cookieless providers
But, let's see what comes out of that.
Visual Studio's Unit Test generator generates a call to Assert.Inconclusive but, usually generates a call to another method of the Assert class. I find that very annoying because, some times, this makes the test fail instead of being reported as inconclusive.
To comment out these extra calls to Assert methods, the following regular expression can be used:
Find what:
{:b*}{Assert\.~(Inconclusive).*\n:b*Assert\.Inconclusive}
Replace with:
Check out the complete list.
I don't like to see constant strings being concatenated in source code. I know the compiler compiles it into a single string, but I think it sends out the wrong message.
However, code generators (like Visual Studio's Unit Test generator) usually generate code with long strings concatenated across several lines of source code.
In order to replace this:
text = "This is a one " + "line concatenation." +
"This is a multiline concatenation."
+ "This is a multiline concatenation."
+
"This is a multiline concatenation with multiple blank lines." +
"This looks like a string concatenation \" + " + "."into this:
text = "This is a one line concatenation.This is a multiline concatenation.This is a multiline concatenation.This is a multiline concatenation with multiple blank lines.This looks like a string concatenation \" + ."
The following regular expression can be used:
Find what:
~(\\)\":b*(:b*\n)*\+(:b*\n)*:b*\"
Replace with:
There's one caveat, though. This Regular expression only works with regular C# string literals. It doesn't work with Visual Basic or @-quoted C# strings.
Check out the complete list.
Visual Studio comes with the a specific set of regular expressions can be used in the Find what field of the its Find and Replace Window . This page is about a few expressions I've been using over time. Find And Replace Patterns Joining Concatenated...
/n software has released version 8.0 of its IP*Works! suite of components for Internet development. Check out what's new here.
The main features of this version are:
- Support of .NET 3.5 syntax changes
- Mocking automatic properties.
- Mocking Anonymous Types.
- Mocking Lambda Expressions.
- Verifying New Initialziers.
- Mocking Extension Methods.
- Mocking LINQ statements.
- Integration API for tools developers
- Tracer Enhancement (Professional Editions)
- NCover 2.0 Support (Professional Editions)
- Support of Visual Studio Orcas Beta 2
More information can be found in the Release Notes
Lattix has upgraded its LDM product:
Lattix LDM for C/C++ now includes an integration with Understand for C++
As part of our Lattix LDM C/C++ solution, we now offer an integration with Understand for C++ from Scitools, leveraging its fast and accurate code analysis capabilities to build the most complete and scalable solution for complex C/C++ systems.
Introducing Lattix LDM for Ada
This new solution enables you to analyze the architecture of any Ada 83 and 95 application in terms of the system elements and their interrelationships (directories, package spec files and package body files). Included with this solution is a module for loading dependency data from Understand for Ada by Scitools.
The P&P team has released another Web Client Software Factory Guidance Bundle. This time is the Validation Guidance Bundle.
What are some scenarios to consider using the guidance in this bundle for?
- Improving UI responsiveness while reusing entity business validation logic across screens when performing validations such as:
- Length of Employee name.
- Employee’s email.
- Order number is unique.
- Order is complete.
- Improving UI responsiveness for applications utilizing Server-Side ASP.NET validators.
- Determining what type of validation to use for improving responsiveness and security.
Who should use this bundle?
This bundle is for Developers and Architects who are interested in improving the UI Responsiveness of validation in their Line-Of-Business ASP.NET Web applications.
What is in the bundle?
- Validation QuickStart: source code to demonstrate how to improve UI responsiveness for validation and reuse of validation rules across pages.
- Validation Application Block from Enterprise Library 3.1: Validation Application Block binary.
- AJAXControlToolkit.WCSFExtensions.dll: Contains the ServerSideValidationExtender which invokes ASP.NET validators including the Enterprise Library PropertyProxyValidator via AJAX
- Acceptance Tests: Manual tests that can be executed to walk you through the Quickstart functionality.
- Documentation: Documentation explaining Validation Guidelines (Security, Schema, and so on) the Quickstart, and how to use the extender.
Check it out. It even has an introduction video (15' - 15MB) by Glenn Block.
Filed under: .NET, Architecture, ASP.NET, Community, SoftDev, C#, Microsoft, MSDN, MVP, Web, WCSF, PnP, SoftwareFactories