ASCENDNET Work Item Rss Feed

Commented Issue: Components Not Showing or Working [33722]

AndreaReade16 — Wed, 30 Jan 2013 17:59:24 GMT

The components are in the toolbox but they're not working or showing up on the Windows form.

Help.

-Andrea
Comments: ** Comment from web user: AndreaReade16 **

How do I fix this bug

Created Issue: Components Not Showing or Working [33722]

AndreaReade16 — Wed, 30 Jan 2013 17:52:13 GMT

The components are in the toolbox but they're not working or showing up on the Windows form.

Help.

-Andrea

Commented Issue: Can not drop controls on designer in Visual Studio 2010 [30343]

EagleLuis — Thu, 29 Dec 2011 15:48:51 GMT

Ascend.net Winforms would not work on designer in Visual Studio 2010.
But these work as expected in Visual Studio 2008. I can drag and drop these controls on designer and change properties etc.
Any help will be greatly appreciated.
Comments: ** Comment from web user: EagleLuis **

I had this problem and it was solved checking that those registry keys did not exists except the first one. Then I have created the last 2 of them and restarted VS 2010 and it worked.

My W7 is 64-bit so these keys are restored in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node instead of HKEY_LOCAL_MACHINE\SOFTWARE\, if you have 32-bit platform just edit the script and take out the \Wow6432Node registry folder.

Here I leave my script:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727\AssemblyFoldersEx\Public Assemblies\Ascend.NET]
@="C:\\Program Files (x86)\\Ascend.NET Project\\Ascend.NET Windows Forms Controls\\version 1.0.0.6\\"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727\AssemblyFoldersEx\Public Assemblies 9\Ascend.NET]
@="C:\\Program Files (x86)\\Ascend.NET Project\\Ascend.NET Windows Forms Controls\\version 1.0.0.6\\"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727\AssemblyFoldersEx\Public Assemblies (Common Files)\Ascend.NET]
@="C:\\Program Files (x86)\\Ascend.NET Project\\Ascend.NET Windows Forms Controls\\version 1.0.0.6\\"

Commented Issue: Can not drop controls on designer in Visual Studio 2010 [30343]

asbadwal — Thu, 09 Jun 2011 03:20:24 GMT

Thanks mate. I will try it soon.

Commented Issue: Can not drop controls on designer in Visual Studio 2010 [30343]

Callesen — Tue, 07 Jun 2011 13:25:30 GMT

I had the same problem (Windows 7 + VS 2010)! Check if Ascend.NET is registered correct (use regedit)!
HEKY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> .NETFramework -> v2.0.50727 -> AssemblyFoldersEx -> Public Assemblies
HEKY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> .NETFramework -> v2.0.50727 -> AssemblyFoldersEx -> Public Assemblies (Common Files)
HEKY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> .NETFramework -> v2.0.50727 -> AssemblyFoldersEx -> Public Assemblies 9

if not make the same registration in all folders and restart.

Commented Issue: doesn't work with vs2010 [28718]

Callesen — Tue, 07 Jun 2011 13:24:27 GMT

Since upgrading to VS2010, I'm unable to add controls to my forms.
I am able to see forms converted from vs2008 though

Any chance of this getting fixes? knowing that this project is somewhat frozen in the past few years

Thanks!
Comments: ** Comment from web user: Callesen **

if not make the same registration in all folders and restart.

Commented Issue: doesn't work with vs2010 [28718]

docco — Mon, 02 May 2011 13:26:47 GMT

@Ztgreve - not sure I understand, the entire solution exists in a single folder (ex: C:\Program Files (x86)\Ascend.NET Project\Ascend.NET Windows Forms Controls\version 1.0.0.6)
What should I copy where?

10x

Created Issue: Can not drop controls on designer in Visual Studio 2010 [30343]

asbadwal — Tue, 15 Mar 2011 02:28:10 GMT

Created Issue: Can not drop controls on designer in Visual Studio 2010 [30342]

asbadwal — Tue, 15 Mar 2011 02:28:07 GMT

Commented Issue: doesn't work with vs2010 [28718]

asbadwal — Tue, 15 Mar 2011 02:20:33 GMT

I am having same issue with controls. These would not work on designer in Visual Studio 2010.
I couldn't understand your solution : which was "I was able to fix the issue by copying the files from Ascend.Design to Ascend.Windows.Forms!!! The designers now work as expected."
Does it mean renaming the Ascend.Design to Ascend.Windows.Forms or soemthing else ?

Commented Issue: doesn't work with vs2010 [28718]

Ztgreve — Fri, 28 Jan 2011 23:25:47 GMT

I was able to fix the issue by copying the files from Ascend.Design to Ascend.Windows.Forms!!! The designers now work as expected.

I hope this helps anyone frustrated with the components and VS2010.

Commented Issue: doesn't work with vs2010 [28718]

Ztgreve — Fri, 28 Jan 2011 23:04:31 GMT

I am having the same issue. I am going to browse the source code and see if I can find anything that might be inhibiting the controls from being used with VS2010.

Created Issue: doesn't work with vs2010 [28718]

docco — Mon, 30 Aug 2010 16:12:11 GMT

Created Issue: Controls are getting added to Non-Visual tray in Sharp Develop.

pkavuri — Tue, 30 Dec 2008 13:20:45 GMT

I am using Sharp Develop for developing my application. When I try to drop any of these (navigation pane) controls on the designer window, these are getting added in Non-Visual tray where as it is getting added in Visual Tray in Visual Studio. This means I am unable to use these controls in Non-Visual studio environment. Do we have to use VS for using these controls?

CREATED ISSUE: Add Visual Studio ToolBox Integration für Ascend.Net Setup

Excel — Sat, 03 May 2008 11:34:57 GMT

At the moment the user das to manuall add the Ascend.Net Controls to the Visual Studio Toolbox after Setup. Would be nice if the setup would ask to do this automatically for the user.

CREATED ISSUE: Fix display behavior when nav pane is resized to a very short height

Pawprint — Mon, 04 Feb 2008 21:37:23 GMT

When the NavigationPane is resized to a height that is less than the height of all buttons combined, it displays...oddly. The easiest way to see this is to put a control on a form, add about 4 pages, and then run the form and shrink it vertically. Then do the same with Outlook 2007 and see how it behaves.

A MinimumHeight property should probably be added to the NavigationPanePage class, or a MinimumPageHeight property to the NavigationPane class if you don't want to allow this to be set at the page level.

CREATED ISSUE: Something basic is missing: Text property

degt — Sun, 17 Jun 2007 15:31:52 GMT

There is something very basic missing in the Outlook navigation pane (and navigationPanePage) and that is the Text property that is kind of standard in all controls. When one places the control on the form with the designer both the pane and the page have some long default name "navigationPaxxxxxxxxxx" and there is absolutely no public property that allows one to change that. The Page control has a "Key" property but that is really very unconventional if that is supposed to be the "caption". There is no caption property either that could perform this function. I therefore have no way to use this control in my application

COMMENTED ISSUE: AddRange with Navigationpanes problem

a94urbjoh — Wed, 28 Mar 2007 21:00:09 GMT

When adding a range with NavigationPanePages objects to an existing NavigationPane only the first one is used to display all the others. Comments: ** Comment from web user: a94urbjoh **

Dont worry about this, it was my fault, I had problems with the naming of the panes.

CREATED ISSUE: AddRange with Navigationpanes problem

a94urbjoh — Wed, 28 Mar 2007 20:41:34 GMT

When adding a range with NavigationPanePages objects to an existing NavigationPane only the first one is used to display all the others.

COMMENTED FEATURE: Add AllowMinimize property to NavigationPane

jeremyjarrell — Thu, 18 Jan 2007 18:36:56 GMT

Add a getter/setter property which determines whether or not the NavigationPane may be minimized/ Comments: ** Comment from web user: jeremyjarrell **

Finished property. No functionality yet.