Luciano Evaristo Guerche

This new article from Ken Getz provides an overview of many of the new features in Visual Basic 2005, including "My", "Edit and Continue", "AutoCorrect", "Just My Code" and more...
Check it out here

“Community Seal of Approval” Blogs (blogs that got at least one recommendation)

If you are getting close to actually porting code, I'd recommend also reading Bill Vaughn's take on the subject, Migrating Code and Concepts from ADO "Classic" to ADO.NET. He comes at it from a more conceptual level - "What are your routines in ADO actually doing, and how can you get the same or better functionality in ADO.NET?" Between the two articles you should be able to get the conceptual underpinnings you'll need to get you started.

I intend to use this post to maintain a listing of Whidbey bloggers.  If you believe that you are blogging useful Whidbey content give me a ping and I'll add you to the list:

Sometimes you may have the string name of an enumeration identifier, and want its enum type. For example, you write a enum identifier as a string to a file and want to read it back and obtain the original enumeration type. This takes place when you serialize a class to an XML file and deserialize it back using XmlSerializer.

I intend to use this post to maintain a listing of Whidbey bloggers.  If you believe that you are blogging useful Whidbey content give me a ping and I'll add you to the list:

I created the following two stored procedures using named transactions inside them

/*
 **********************************************************
 */
CREATE PROCEDURE #WorkingWithNamedTransactionsOne
-- This procedure does not raise error
AS
DECLARE @ERROR bit
 
PRINT 'Starting NamedTransactionOne'
BEGIN TRANSACTION NamedTransactionOne
SET @ERROR = 1
PRINT 'NamedTransactionOne started'
 
-- SOME TSQL statement here
 
IF @@ERROR <> 0
BEGIN
    GOTO WorkingWithNamedTransactionsOne_Finally
END
 
-- SOME TSQL statement here
 
IF @@ERROR <> 0
BEGIN
    GOTO WorkingWithNamedTransactionsOne_Finally
END
 
PRINT 'Committing NamedTransactionOne'
COMMIT TRANSACTION NamedTransactionOne
SET @ERROR = 0
PRINT 'NamedTransactionOne committed'
 
 
WorkingWithNamedTransactionsOne_Finally:
IF @ERROR = 1
BEGIN
    PRINT 'Rolling back NamedTransactionOne'
    ROLLBACK TRANSACTION NamedTransactionOne
    SET @ERROR = 0
    PRINT 'NamedTransactionOne rolled back'
END
RETURN
GO
 
/*
 **********************************************************
 */
CREATE PROCEDURE #WorkingWithNamedTransactionsTwo
-- This procedure raises error
AS
DECLARE @ERROR bit
 
PRINT 'Starting NamedTransactionOne'
BEGIN TRANSACTION NamedTransactionOne
SET @ERROR = 1
PRINT 'NamedTransactionOne started'
 
-- SOME TSQL statement here
 
IF @@ERROR <> 0
BEGIN
    GOTO WorkingWithNamedTransactionsTwo_Finally
END
 
SELECT 1/0 AS [This might raise an error]
 
IF @@ERROR <> 0
BEGIN
    GOTO WorkingWithNamedTransactionsTwo_Finally
END
 
PRINT 'Committing NamedTransactionOne'
COMMIT TRANSACTION NamedTransactionOne
SET @ERROR = 0
PRINT 'NamedTransactionOne committed'
 
 
WorkingWithNamedTransactionsTwo_Finally:
IF @ERROR = 1
BEGIN
    PRINT 'Rolling back NamedTransactionOne'
    ROLLBACK TRANSACTION NamedTransactionOne
    SET @ERROR = 0
    PRINT 'NamedTransactionOne rolled back'
END
RETURN
GO

/*
 **********************************************************
 */
EXECUTE #WorkingWithNamedTransactionsOne
GO
 
EXECUTE #WorkingWithNamedTransactionsTwo
GO
 
BEGIN TRANSACTION
EXECUTE #WorkingWithNamedTransactionsOne
COMMIT TRANSACTION
GO
 
BEGIN TRANSACTION
EXECUTE #WorkingWithNamedTransactionsTwo --ATTENTION: Server: Msg 6401, Level 16, State 1
 - Cannot roll back NamedTransactionOne. No transaction or savepoint of that name was found.
COMMIT TRANSACTION
GO

/*
 **********************************************************
 */
CREATE PROCEDURE #WorkingWithNamedTransactionsAndSavepointsOne
-- This procedure does not raise error
AS
DECLARE @ERROR int
 
PRINT 'Starting NamedTransactionOne'
BEGIN TRANSACTION NamedTransactionOne
PRINT 'NamedTransactionOne started'
 
PRINT 'Starting NamedSavepointOne'
SAVE TRANSACTION NamedSavepointOne
PRINT 'NamedSavepointOne started'
 
-- SOME TSQL statement here
 
SET @ERROR = @@ERROR
IF @ERROR <> 0
BEGIN
    GOTO WorkingWithNamedTransactionsAndSavepointsOne_Finally
END
 
-- SOME TSQL statement here
 
SET @ERROR = @@ERROR
IF @ERROR <> 0
BEGIN
    GOTO WorkingWithNamedTransactionsAndSavepointsOne_Finally
END
 
 
WorkingWithNamedTransactionsAndSavepointsOne_Finally:
IF @ERROR <> 0
BEGIN
    PRINT 'Rolling back NamedSavepointOne'
    ROLLBACK TRANSACTION NamedSavepointOne
    PRINT 'NamedSavepointOne rolled back'
END
 
PRINT 'Committing NamedTransactionOne'
COMMIT TRANSACTION NamedTransactionOne
PRINT 'NamedTransactionOne committed'
 
RETURN
GO
 
/*
 **********************************************************
 */
CREATE PROCEDURE #WorkingWithNamedTransactionsAndSavepointsTwo
-- This procedure raises error
AS
DECLARE @ERROR int
 
PRINT 'Starting NamedTransactionOne'
BEGIN TRANSACTION NamedTransactionOne
PRINT 'NamedTransactionOne started'
 
PRINT 'Starting NamedSavepointOne'
SAVE TRANSACTION NamedSavepointOne
PRINT 'NamedSavepointOne started'
 
-- SOME TSQL statement here
 
SET @ERROR = @@ERROR
IF @ERROR <> 0
BEGIN
    GOTO WorkingWithNamedTransactionsAndSavepointsTwo_Finally
END
 
SELECT 1/0 AS [This might raise an error]
 
SET @ERROR = @@ERROR
IF @ERROR <> 0
BEGIN
    GOTO WorkingWithNamedTransactionsAndSavepointsTwo_Finally
END
 
WorkingWithNamedTransactionsAndSavepointsTwo_Finally:
IF @ERROR <> 0
BEGIN
    PRINT 'Rolling back NamedSavepointOne'
    ROLLBACK TRANSACTION NamedSavepointOne
    PRINT 'NamedSavepointOne rolled back'
END
 
PRINT 'Committing NamedTransactionOne'
COMMIT TRANSACTION NamedTransactionOne
PRINT 'NamedTransactionOne committed'
 
RETURN
GO

/*
 **********************************************************
 */
EXECUTE #WorkingWithNamedTransactionsAndSavepointsOne
GO
 
EXECUTE #WorkingWithNamedTransactionsAndSavepointsTwo
GO
 
BEGIN TRANSACTION
EXECUTE #WorkingWithNamedTransactionsAndSavepointsOne
COMMIT TRANSACTION
GO
 
BEGIN TRANSACTION
EXECUTE #WorkingWithNamedTransactionsAndSavepointsTwo
COMMIT TRANSACTION
GO

From the capable group at Vertigo Software (the same folks who produced the venerable IBuySpy and Quake II .NET) comes FotoVision, a suite of applications that allow you to organize and manipulate digital photos and share them on a web site. A full Windows Forms desktop client is provided, along with an ASP.NET web site that exposes some Web Services, and a Pocket PC application that leverages the .NET Compact Framework. Additionally, there are a number of good white papers that explain the architecture and technology behind the solutions. And if that isn’t enough, the full source code for all three applications is provided in Visual Basic .NET (included in the installation).