Bugs Area Requirement Alternatives Code by xiagong0815

VIEWS: 1 PAGES: 11

									Area                    Requirement / Alternatives


Code conversion to VB   How to handle solutions conversion


Code conversion to VB   How to handle imports in VB code
Code conversion to VB   How to handle imports in VB code
Folder Structure        Add VB solutions to lab



                        Give instructions on how to create the begin
Document Update
                        solution




Document Update         Instructions or screenshots update




Document Update         Instructions or screenshots update



Document Update         Document code snippets



Document Update         Instructions or screenshots update


Document Update         References to figure numbers in the document

                        Use the Handles keyword instead of AddHandler
code conversion to VB
                        statement.
Decision
• We will use InstantVB tool for converting C# code to VB, following the approach Drew suggested:
o Convert the begin solution
o Convert each code snippet of the document
o Follow the lab applying those code snippets to build end solution
Use "Remove Common namespace" option of InstantVB
Use project level imports whenever posible
Create VB and C# subdirectories in the Start and End folders, for the VB & C# solutions

Do not point the user to use a specific folder (C# or VB) when creating a new solution. For example:
"2. Create a new project in Visual Studio 2010 of type Sequential Workflow Console Application (under the
Workflow project type) selecting the language of your preference (Visual C# or Visual Basic). Ensure .NET
Framework 4 is selected as the target runtime, and name it HelloWorkflow. Name the solution Begin, set the
desired location, and click OK."


Treat C# and VB in an unbiased way:
* "2. Open the starting solution Begin.sln located under
%TrainingKitInstallationfolder%\Labs\MonitoringWokrflow\Ex1-BasicMonitoring\Begin folder, choosing the
language of your preference (C# or VB). "
* "1. In Visual Studio 2010, open GetStockPrice.cs (C#) or GetStockPrice.vb (Visual Basic)."


Screenshots should be duplicated wherever the VB flow of the lab differs from the C# flow.

Use Csharp or VB in the code snippet title, as follows:
(Code Snippet – Introduction to WF Lab - SayHelloInCode Class CSharp)
or
(Code Snippet – Introduction to WF Lab - SayHelloInCode Class VB)
Instructions for only one group of user should be tagged as shown below:
"(For Visual Basic Users) The above code snippet uses implicit typing. You will need to set 'Option Infer On' in the
VB file or set 'Option Infer' at the project level."
If it is possible, use "the previous figure" or "the following figure" to refer to screenshots.
Whenever it is possible we will use the Handles keyword instead of the AddHandler, this involves: declaring the
field as "WithEvents", not adding the event handler as C# does, and add the "Handles" keyword in the event
handler method declaration.
Underlying principles


Approach Proposed


VB Guidelines
Requirement
Consistency with other Labs




Consistency with other Labs




Requirement




Requirement



Consistency with other Labs



Clarity

Avoid problems with figure
numbering.

VB Guidelines
ID CU   WorkArea
 1      FE (Registrarse)
 2
Descripción
Al ingresar la fecha de nacimiento, solo deja ingresar en formato DD-MM-
AAAA
Solución Propuesta                                  Severidad       Solucionado   Levantado Por
1) Agregar que pueda agregarse con otros formatos               1                 skehoe
Spent (hs)

								
To top