scsfcontrib Work Item Rss Feed

Created Issue: CAB UI is not working in Windows 7 and Vista operating systems [16972]

ksreddy77 — Thu, 25 Mar 2010 18:21:34 GMT

Hi,

Installing the CAB UI in is not working in Windows 7 and Vista operating systems(It's working in the XP). How to resolve this issue?

Thnaks,
KSREDDY

Created Issue: Dragging an item to docked pinned down window does not open the window

AnmolArya — Tue, 21 Apr 2009 07:07:22 GMT

HI,

I have a custom clipboard area in my application as right docked window (similar to Solution explorer in Visual Studio 2008). When this docked window is pinned down and I drag an item to it, it does not get open. Do you have any solution for this?

Thanks for you help in advance

Created Issue: Add business module and View error

yuxinbo — Tue, 14 Apr 2009 04:11:46 GMT

Hi Team,

I am working using SCSF 2008 and SCSF Contrib 1.5.

I try to create project base on TestSuite.sln in sample of SCSF Contrib. When I try to add business module, I encounter error below and I couldn't create view in module because there is no Add View menu when I right click on Views folder.

An exception occurred during the binding of reference or execution of recipe CreateBusinessModuleCS .Error was: An error happened while calling the value provider or evaluating the default value of argument ShellProj..
You can remove the reference to this recipe through the Guidance Package Manager .

-------------------------------------------------------------------------------------------------------------------
Microsoft.Practices.RecipeFramework.ValueProviderException: An exception occurred during the binding of reference or execution of recipe CreateBusinessModuleCS. Error was: An error happened while calling the value provider or evaluating the default value of argument ShellProject..
You can remove the reference to this recipe through the Guidance Package Manager. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Practices.SmartClientFactory.ValueProviders.GetProjectFromGuidProvider.OnBeginRecipe(Object currentValue, Object& newValue)
at Microsoft.Practices.RecipeFramework.Recipe.CallProviders(IDictionary providers, IDictionaryService readonlyArguments, IDictionaryService arguments, Boolean isBefore)
--- End of inner exception stack trace ---
at Microsoft.Practices.RecipeFramework.Recipe.CallProviders(IDictionary providers, IDictionaryService readonlyArguments, IDictionaryService arguments, Boolean isBefore)
at Microsoft.Practices.RecipeFramework.Recipe.Execute(Boolean allowSuspend)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(String recipe, IAssetReference reference, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.GuidancePackage.ExecuteFromTemplate(String recipe, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate.ExecuteRecipe(Boolean executeActions)
at Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate.RunStarted(Object automationObject, Dictionary`2 replacementsDictionary, WizardRunKind runKind, Object[] customParams)
-------------------------------------------------------------------------------------------------------------------

I am looking forward to head from you.

Best wishes

Dio yu

Commented Issue: "Add View (With presenter)" menu doesn't show on VS2008SP1

jschmiede — Wed, 11 Feb 2009 20:50:37 GMT

I am following the get started, but it turned out the "Add View (With presenter)" doesn't show up. anyone can help me?
Comments: ** Comment from web user: jschmiede **

Hi it is a known issue http://www.codeplex.com/smartclient/Wiki/View.aspx?title=Known%20Issues%3a%20SC-SF%20April%202008%20with%20Visual%20Studio%202008%20and%20SP1%20Beta&referringTitle=Known%20Issues%20%2f%20Fixes#RecipesNotDisplayed

Created Issue: "Add View (With presenter)" menu doesn't show on VS2008SP1

benny856694 — Tue, 10 Feb 2009 03:24:59 GMT

I am following the get started, but it turned out the "Add View (With presenter)" doesn't show up. anyone can help me?

Created Issue: TestSuite Example problem

bobmre — Tue, 23 Dec 2008 16:22:29 GMT

Has anyone noticed that the about box does not show the loaded modules once you open a rtf document?

COMMENTED FEATURE: Implement a guidance package that works with WPF CAB layer

gblock — Thu, 01 May 2008 06:51:35 GMT

Implement the latest guidance package from the Smart Client Factory but using the WPF CAB layer.
Comments: ** Comment from web user: gblock **

http://www.codeplex.com/SCSFWPF has a GP for using WPFCAB

COMMENTED FEATURE: Implement a guidance package that works with WPF CAB layer

kmorris — Tue, 29 Apr 2008 17:10:15 GMT

Implement the latest guidance package from the Smart Client Factory but using the WPF CAB layer.
Comments: ** Comment from web user: kmorris **

I think the impact of this should be higher than Medium. Not having guidance automation will slow adoption significantly.

COMMENTED ISSUE: EnableModelessKeyboardInterop so keyboard works in dialogs

SimonCropp — Thu, 17 Apr 2008 23:26:07 GMT

I just added a EnableModelessKeyboardInterop call to SCSFContrib.CompositeUI.WPF\Workspaces\WindowWorkspace.cs to work around this problem http://channel9.msdn.com/ShowPost.aspx?PostID=339446. Altered code shown below.
Any chance of getting this checked into the trunk?

private Window CreateWindow(object smartPart)
{
Debug.Assert(!_windows.ContainsKey(smartPart));
Window window = new Window();
ElementHost.EnableModelessKeyboardInterop(window);
window.Content = smartPart;

window.Closing += delegate(object sender, System.ComponentModel.CancelEventArgs e)
{
RaiseSmartPartClosing(e);
};

window.Closed += delegate
{
_windows[smartPart].Content = null;
_windows.Remove(smartPart);
InnerSmartParts.Remove(smartPart);
};

_windows[smartPart] = window;
return window;
}
Comments: ** Comment from web user: SimonCropp **

bump

CREATED ISSUE: EnableModelessKeyboardInterop so keyboard works in dialogs

SimonCropp — Sun, 30 Mar 2008 10:43:02 GMT

CREATED ISSUE: Bug in Wpf Visualizer

DumbClient — Tue, 22 Jan 2008 12:01:32 GMT

There's a (simple) bug in the *WorkItemHelper* class used in the new (and very useful) *WpfVisualizer* which causes incorrect display of the WorkItem hierarchy.
The problem and 2 solutions are explained here: [http://www.codeplex.com/scsfcontrib/Thread/View.aspx?ThreadId=16913]

CREATED ISSUE: Make solutions work with Visual Studio Express editions (2008)

tappm — Thu, 10 Jan 2008 18:33:40 GMT

The solution item folders defined in the solutions (src or samples) prevent compilation with Visual Studio 2008 Express Edition.

CREATED ISSUE: WpfCommand not sharing input gestures with attached ICommand

tappm — Thu, 10 Jan 2008 18:30:50 GMT

The WpfCommand in CommandService does not use the input gestures of the possible RoutedCommand from the passed WPF.ICommand. The attached file corrects this.

CREATED ISSUE: SCSFContrig.CompositeUI Links with System.Windows.Forms & Microsoft.Practices.CompositeUI.WinForms

tappm — Thu, 15 Nov 2007 19:29:11 GMT

Hi,

the SCSFContrig.CompositeUI project references windows forms assemblies:
- System.Windows.Forms
- Microsoft.Practices.CompositeUI.WinForms

This appends because of the UserControl reference in the Visualizer which is defined in SCSFContrig.CompositeUI.

Please remove these references as they are not needed.

Thanks

CREATED TASK: VS2008 support for Solution files

matiaswoloski — Mon, 22 Oct 2007 01:49:10 GMT

Solutions should work on VS2008

Steps required to implement this:
* Clone your solution file, typically ending it with "VS2008.sln" to make it explicit that this is the "beta" solution file.
* Open in VS2008, and complete the upgrade wizard. This will remove from the project files the MSBuild import of WPF targets, as they are built-in VS2008.
* Close the solution, and open each project file with a text/XML editor. Towards the end of the file, add the following Import:

<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
<Import Project="$(MSBuildBinPath)\Microsoft.WinFX.targets" />
</Project>

CREATED FEATURE: Implement a guidance package that works with WPF CAB layer

matiaswoloski — Mon, 22 Oct 2007 01:37:56 GMT

Implement the latest guidance package from the Smart Client Factory but using the WPF CAB layer.

CREATED ISSUE: WindowWorkspace bug

SqlRanger — Sun, 23 Sep 2007 21:11:51 GMT

WindowWorkspace.CreateWindow mehtod has a litle bug. It calls RaiseSmartPartClosing(e) but it should be RaiseSmartPartClosing(smartPart).

CREATED ISSUE: UIElementCommandAdapter malfunction

SqlRanger — Sun, 23 Sep 2007 10:06:02 GMT

If a command invoker is added for a disabled command, the UIElement appears enabled. This is beacuase UIElementCommandAdapter does not overrides BindCommand method.

This is my suggested code:

public override void BindCommand(Command command)
{
base.BindCommand(command);
foreach (UIElement key in Invokers.Keys)
{
key.IsEnabled = (command.Status == CommandStatus.Enabled);
key.Visibility = (command.Status == CommandStatus.Unavailable) ? Visibility.Collapsed : Visibility.Visible;
}
}

CLOSED ISSUE: Add Separator UI Extension Support

kentcb — Thu, 16 Aug 2007 09:45:46 GMT

Add support for treating Separator controls as UI extensibility points, as per the Winforms layer and as per this request: http://www.codeplex.com/scsfcontrib/Thread/View.aspx?ThreadId=13739
Comments: Added ItemsControlChildUIAdapter, which allows a child of an ItemsControl to be used as a UI extensibility point.

CREATED ISSUE: Add Separator UI Extension Support

kentcb — Wed, 15 Aug 2007 13:38:17 GMT

Add support for treating Separator controls as UI extensibility points, as per the Winforms layer and as per this request: http://www.codeplex.com/scsfcontrib/Thread/View.aspx?ThreadId=13739