| M Sheik's profileudooz!PhotosBlogLists |  Tools  Help |
|
|
March 09 A war between Team Foundation API and me - Part IIHi!
Finally, i've concluded that instead of WSS, it is better to use Microsoft Visual Studio Team Foundation Server API in our application. TFS might decrease our application's features localization, but it will reduce my headache. It is actually built on top of WSS. So we can enjoy the share point services with luxury of TFS. Okay! let me write some sample applications to test the TFS APIs before the production code. I've got the following dlls from Visual Studio 2005 SDK. You can download VS2005 SDK from http://www.vsipdev.com/downloads.At the time of downloading, Microsoft released VS2005 SDK Feb 2005 CTP. So, i've downloaded the SDK and installed it on my machine.
VS2005 SDK Feb 2006 CTP:
After the installation, i navigated to Visual Studio 2005 SDK > 2006.02 > Visual Studio Team System Integration from my Program Folder Menu. It has some samples and documentation for VSTS Integration. Really i hate the documentation which is in Word document and unable to see the ever green Microsoft help style. No explanations, code snippets for VSTS SDK.
And i was shocked, because these documents does not help you to explore from where you can start to develop. One fine day, i ran Lutz Roder's .NET Reflector and decompile the following TFS assemblies.
In Microsoft.TeamFoundation, i found namespace Microsoft.TeamFoundation.Proxy.Portal which contains most of the basic APIs to create a project and work items on Team Foundation Server from your application. (See Fig 1).
The classes and methods are self explanatory, so i've decided to use those assemblies. But after a while, i was strucked when using this API. I cannot understand most of the parameters for some basic functions. Oh God! Now i am searching again for help...i got help for TFS Version Control APIs only. After that, I found that microsoft released VS2005 SDK March 2006 CTP. Still no more improvements from me. So guys! let me take some times. I will meet on next issues with a solution.
 February 22 A War Between SharePoint SDK and MeCurrently, in our secondary activity, we are developing a web application which will automate our research prototypes lifecycle. In these, there are numerous documents, codes and reviews are generated, so that we are planned to use WSPS (Windows SharePoint Services) SDK for document management in our portal.
Once again, we've no plan to use the ready made Share Point Portal Server, any way, that is not the solution for our portal. Instead, we planned to use Windows SharePoint Services as like as Visual Studio Team Foundation Server uses WSPS.
So, in our service agent component, i need to provide a solution to access Windows SharePoint Services from my business objects.
I've confused to take a decision whether to provide service agent for black forest flavoured Team Foundation Foundation Server or venilla flavoured WSPS.
Order one Venilla - Try to defeat this.
First i downloaded WSPS SDK from microsoft site. I got bored to read full SDK documentation, so i googled some samples for WSPS in document management. I'm unable to found one which is matched our requirement. Smell the black forest - Why can't we try.
So, i decided that TFS will be the mail life cycle, then why can't we try to manage TFS from our service agent. I've collected some document about Team Foundation Server Object Model and read some blogs. Ohhh!! I want some pain-relief balm.
So, guys! let me explain the remaing stories of my war with WSPS in the forethcoming articles. February 14 Sometimes Reverse Engineering makes life easierWe, the IT guys always pray the GOD to save us from reverse engineering works, because it may be a bomb or bubble.
But one day for me, it was not only a bubble. It makes our life easier. Actually, myself and my friend rajesh were assigned to create a data model for a project within a short period (5 hrs which includes tea break/smoke break).
Though, functional specification and use-case model were the only inputs for our data model. So, rajesh told me an idea. Instead of creating data model in Visio, it is better to create data table in target database server. I agreed and opened SQL Management Studio (SQL 2005).
[Note: Because of the urgent requirement of data model, instead of designing it by the use of Design specification, we actually used functional specificationa and use cases]
Based on functional specification and use-case model, we were created all tables and finally we got Visio data model. How? It is very simple.
1. We opened SQL 2005 Management Studio.
2. Based on first use case, we've created three tables. 3. Then, opened the diagram section of the Database. 4. Imported those three tables. 5. By the use of Diagram, we formed constraints of the tables. Repeat the steps 2...5 for all use cases. Okay, now i would like to tell the actual reverse engineering bubble.
After defining tables and their relationships, we opened Visio.
0. Create a System Datasource for SQL 2005 on your machine.
1. Create a new Data Model Diagram document by New>Database>Database Model Diagram.
2. Select Database>Reverse Engineer.
3. In the steps of wizard, select the system data source.
4. Select necessary options on various steps.
5. Now the Visio creates perfect data model diagram for your project.
Ya! Our project life is simple and perfect. January 31 VS2005 eXPeriences - Part IIHi!
In the previous issue, i've written two comments about VS2005.
The others are...
3) Problem with 3rd Party Web Parts
In ASP.NET 2.0, there is a feature called Wep Parts. It is an integrated set of UI elements for creating a web site that enable users to modify the content, appearance and behaviour of web pages from the client side.
Visual Studio 2005's VWE (Visual Web Editor) let me allow to design web pages using web parts in a flexible manner until you are using the ASP.NET controls.
In our case, we need to use a third party components in our web pages. After adding that third party component on Web Part Zone, the designer mode of the page was locked.
I don't know which one creates problem, because that third party component is web part qualifiable. At the time of development, we did not develop and test with our own web component. So, let me give some time to evaluate this problem.
4) TFS Confusion about version confliction.
Everybody know the Visual Studio Team system. It is maintained and controlled by Team Foundation Server (TFS). The Team system contains its own version control system. Its usage is very compact.
But in Source Control Explorer (which is an explorer in VS2005 IDE to access files and projects in TFS), Invalid Handle message is appeared when version confliction between server and local version of a file.
To force check-in this file, you need to right-click the file on check-in dialog window and select properties. After that, do the check-in. The resolve dialog window is appeared. Resolve it and check-in it.
January 27 eXPerience with VS2005 - Part I
Quote Feedback for VS2005 |
|
|
