![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | WorkItemFormControl - Linked Work Items opened as HTML documents Hi people... I integrated WorkItemFormControl with my application and it works as expected except one little detail: if some work Item have another WI or Changset attached as a link (Links tab), linked items will always be opened as HTML read-only documents. If you do the same action from the Team Explorer, result will be alive Work Item opened in a new WorkItemFormControl window. Is there a way to simulate Team Explorer functionallity from the custom form with hosted WorkItemFormControl control? Thanks in advance, Sasa |
My System Specs![]() |
| | #2 (permalink) |
| | Re: WorkItemFormControl - Linked Work Items opened as HTML documents As long as the target machines you intend to run your application on have Team Explorer installed on them, yes it's possible. I've actually got a project out on CodePlex that I integrated their form into my application already if you need a working example. http://www.codeplex.com/NException Check out the EditTFSWorkItemForm class, it should have a good example of how to use it. Also, from my experience with TFS and custom applications you *will* run into problems with using their controls on forms. The controls you'll be using aren't registered in the GAC *cough* so your application will have problems resolving where the assemblies are located when using them on your target machines. That's the workaround I came up with to ensure the assemblies could be resolved properly (it's inside the Program.cs file in the project I directed you to) static Assembly CurrentDomain_AssemblyResolve(object sender, ResolveEventArgs args) { AssemblyName name = new AssemblyName(args.Name); using (RegistryKey key = Registry.LocalMachine.OpenSubKey(@"Software\Microsoft\VisualStudio\9.0")) { // Locate the installation directory for Visual Studio. string installDir = key.GetValue("InstallDir").ToString(); string privateAssembliesFolder = Path.Combine(installDir, "PrivateAssemblies"); string assemblyFile = Path.Combine(privateAssembliesFolder, name.Name + ".dll"); if (File.Exists(assemblyFile)) { return Assembly.LoadFile(assemblyFile, AppDomain.CurrentDomain.Evidence); } } return null; } "SasaT" <SasaT@xxxxxx> wrote in message news:F9C09C9A-0DF7-4462-90E3-4FF929879D44@xxxxxx Quote: > Hi people... > > I integrated WorkItemFormControl with my application and it works as > expected except one little detail: if some work Item have another WI or > Changset attached as a link (Links tab), linked items will always be > opened > as HTML read-only documents. > > If you do the same action from the Team Explorer, result will be alive > Work > Item opened in a new WorkItemFormControl window. > > Is there a way to simulate Team Explorer functionallity from the custom > form > with hosted WorkItemFormControl control? > > Thanks in advance, > Sasa > |
My System Specs![]() |
| | #3 (permalink) |
| | Re: WorkItemFormControl - Linked Work Items opened as HTML documen Hi Jeff, thanks for helping. I downloaded your project and checked out EditTFSWorkItemForm class, but can not see any parameter which changes default WorkItemFormControl behaviour and opens linked work items in a new WorkItemFormControl window instead as HTML read-only documents. Can you explain me which property/method call/anything ensures that linked work items are opened as editable WorkItemFormControl controls? Thanks, Sasa |
My System Specs![]() |
| | #4 (permalink) |
| | Re: WorkItemFormControl - Linked Work Items opened as HTML documen Ah sorry, must've been a little tired when i answered that the other day. Can't say i've ever tried using the control to open up linked work items before. There might be something in the TFS SDK about it, but i doubt it. Sorry i couldn't be of more help "SasaT" <SasaT@xxxxxx> wrote in message news:3A5CC18E-3673-46FB-99EA-282A7B7DA95C@xxxxxx Quote: > Hi Jeff, > > thanks for helping. > I downloaded your project and checked out EditTFSWorkItemForm class, but > can > not see any parameter which changes default WorkItemFormControl behaviour > and > opens linked work items in a new WorkItemFormControl window instead as > HTML > read-only documents. > > Can you explain me which property/method call/anything ensures that linked > work items are opened as editable WorkItemFormControl controls? > > Thanks, > Sasa |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Cant Print Excel HTML linked documents on Vista | Microsoft Office | |||
| TFS 2008 Process Template: Default value tag for work item fieldsdoes not allow more than 255 characters to be entered into an HTML control | .NET General | |||
| Previews of html documents in Windows Explorer | Vista General | |||
| HTML <OPTION SELECTED> Doesn't work in Vista machine | Vista General | |||
| DSN Doesn't Work with Documents Folder | Vista General | |||