Web Connection
Missing WC controls in VS
Gravatar is a globally recognized avatar based on your email address. Missing WC controls in VS
  Michael Hogan (Ideate Hosting)
  All
  Nov 25, 2014 @ 10:04am
I have a client who has had their wc controls disappear in VS. You can see them if you 'show all' but they are disabled, and we are getting the following message after adding them:

the following controls were successfully added to the toolbox but are not enabled in the active designer

The file extension for the active web page is .kjdp and the extension is included in tools/options/text editor/file extension as 'Web Forms Editor'. The path to the files is not particularly long and does not include spaces or weird characters.

If I add a new page with a wcsx extension, they appear properly. Should we even be using extensions for these page definitions, or does webconnect handle mappings in another way?

Michael
www.WebConnectionHosting.com

Gravatar is a globally recognized avatar based on your email address. Re: Missing WC controls in VS
  Rick Strahl
  Michael Hogan (Ideate Hosting)
  Nov 25, 2014 @ 03:44pm

If you have a non-WCSX file the extension needs to be mapped. When you create a project/process Web Connection will create the highlighting in Visual Studio. If you don't (or move to another machine) you'll have to manually add the extension. See the help file for the VS configuration - it's Text Editor File Extensions I believe under Tools.

As to controls not showing I'm nto sure why that is. I know in VS 2013, VS 2013 Community Editor and VS 2015 the controls no longer install by default as microsoft has removed the APIs to install controls through a public non VSIP API. So this has to be done manually now by either adding the WebConnectionControls project to your solution and then adding a reference to the WebControl project from the Web project. This should automatically show the controls in the toolbox.

Otherwise you can import the controls into the toolbox by adding a tab, then adding components via the DLL component picker.

All this is described in more detail in the help file under the Visual Studio configuration topic.


+++ Rick ---


I have a client who has had their wc controls disappear in VS. You can see them if you 'show all' but they are disabled, and we are getting the following message after adding them:

the following controls were successfully added to the toolbox but are not enabled in the active designer

The file extension for the active web page is .kjdp and the extension is included in tools/options/text editor/file extension as 'Web Forms Editor'. The path to the files is not particularly long and does not include spaces or weird characters.

If I add a new page with a wcsx extension, they appear properly. Should we even be using extensions for these page definitions, or does webconnect handle mappings in another way?



Rick Strahl
West Wind Technologies

Making waves on the Web
from Maui

Gravatar is a globally recognized avatar based on your email address. Re: Missing WC controls in VS
  Michael Hogan (Ideate Hosting)
  Rick Strahl
  Nov 26, 2014 @ 07:13am
Since adding a page with the WCSX extension rather than KJDB allows the controls to display and work properly and since the controls display as disabled when using the KJDB extension (when I 'show all' in the toolbox), it's clearly not a control registration problem but rather the association of the controls with the kjdb file type during the tutorial process. My client says it was initially working, and I have removed and re-added the file type in tools/options/text editor/file extension to no avail.

My client is understandably concerned that it will occur in the middle of a real WebConnect project. I'll post here if I find a solution.

If you have a non-WCSX file the extension needs to be mapped. When you create a project/process Web Connection will create the highlighting in Visual Studio. If you don't (or move to another machine) you'll have to manually add the extension. See the help file for the VS configuration - it's Text Editor File Extensions I believe under Tools.

As to controls not showing I'm nto sure why that is. I know in VS 2013, VS 2013 Community Editor and VS 2015 the controls no longer install by default as microsoft has removed the APIs to install controls through a public non VSIP API. So this has to be done manually now by either adding the WebConnectionControls project to your solution and then adding a reference to the WebControl project from the Web project. This should automatically show the controls in the toolbox.

Otherwise you can import the controls into the toolbox by adding a tab, then adding components via the DLL component picker.

All this is described in more detail in the help file under the Visual Studio configuration topic.


+++ Rick ---


I have a client who has had their wc controls disappear in VS. You can see them if you 'show all' but they are disabled, and we are getting the following message after adding them:

the following controls were successfully added to the toolbox but are not enabled in the active designer

The file extension for the active web page is .kjdp and the extension is included in tools/options/text editor/file extension as 'Web Forms Editor'. The path to the files is not particularly long and does not include spaces or weird characters.

If I add a new page with a wcsx extension, they appear properly. Should we even be using extensions for these page definitions, or does webconnect handle mappings in another way?




Michael
www.WebConnectionHosting.com

Gravatar is a globally recognized avatar based on your email address. Re: Missing WC controls in VS
  Rick Strahl
  Michael Hogan (Ideate Hosting)
  Nov 26, 2014 @ 01:34pm
Michael,

There's nothing special about the WCSX extension. So that should work the same. There are problems in VS with extensions 'going away' and you may have to recreate them. The important thing about that is that you have to remove them first, exit the dialog, then go back into the dialog to add it back. If you don't do this the value doesn't get properly registered.

+++ Rick ---



Since adding a page with the WCSX extension rather than KJDB allows the controls to display and work properly and since the controls display as disabled when using the KJDB extension (when I 'show all' in the toolbox), it's clearly not a control registration problem but rather the association of the controls with the kjdb file type during the tutorial process. My client says it was initially working, and I have removed and re-added the file type in tools/options/text editor/file extension to no avail.

My client is understandably concerned that it will occur in the middle of a real WebConnect project. I'll post here if I find a solution.

If you have a non-WCSX file the extension needs to be mapped. When you create a project/process Web Connection will create the highlighting in Visual Studio. If you don't (or move to another machine) you'll have to manually add the extension. See the help file for the VS configuration - it's Text Editor File Extensions I believe under Tools.

As to controls not showing I'm nto sure why that is. I know in VS 2013, VS 2013 Community Editor and VS 2015 the controls no longer install by default as microsoft has removed the APIs to install controls through a public non VSIP API. So this has to be done manually now by either adding the WebConnectionControls project to your solution and then adding a reference to the WebControl project from the Web project. This should automatically show the controls in the toolbox.

Otherwise you can import the controls into the toolbox by adding a tab, then adding components via the DLL component picker.

All this is described in more detail in the help file under the Visual Studio configuration topic.


+++ Rick ---


I have a client who has had their wc controls disappear in VS. You can see them if you 'show all' but they are disabled, and we are getting the following message after adding them:

the following controls were successfully added to the toolbox but are not enabled in the active designer

The file extension for the active web page is .kjdp and the extension is included in tools/options/text editor/file extension as 'Web Forms Editor'. The path to the files is not particularly long and does not include spaces or weird characters.

If I add a new page with a wcsx extension, they appear properly. Should we even be using extensions for these page definitions, or does webconnect handle mappings in another way?






Rick Strahl
West Wind Technologies

Making waves on the Web
from Maui

Gravatar is a globally recognized avatar based on your email address. Re: Missing WC controls in VS
  Michael Hogan (Ideate Hosting)
  Rick Strahl
  Nov 26, 2014 @ 02:05pm
Aha - that's something I didn't do (remove first, exit the dialog, add it back). Thanks a ton for the tip!


Michael,

There's nothing special about the WCSX extension. So that should work the same. There are problems in VS with extensions 'going away' and you may have to recreate them. The important thing about that is that you have to remove them first, exit the dialog, then go back into the dialog to add it back. If you don't do this the value doesn't get properly registered.

+++ Rick ---



Since adding a page with the WCSX extension rather than KJDB allows the controls to display and work properly and since the controls display as disabled when using the KJDB extension (when I 'show all' in the toolbox), it's clearly not a control registration problem but rather the association of the controls with the kjdb file type during the tutorial process. My client says it was initially working, and I have removed and re-added the file type in tools/options/text editor/file extension to no avail.

My client is understandably concerned that it will occur in the middle of a real WebConnect project. I'll post here if I find a solution.

If you have a non-WCSX file the extension needs to be mapped. When you create a project/process Web Connection will create the highlighting in Visual Studio. If you don't (or move to another machine) you'll have to manually add the extension. See the help file for the VS configuration - it's Text Editor File Extensions I believe under Tools.

As to controls not showing I'm nto sure why that is. I know in VS 2013, VS 2013 Community Editor and VS 2015 the controls no longer install by default as microsoft has removed the APIs to install controls through a public non VSIP API. So this has to be done manually now by either adding the WebConnectionControls project to your solution and then adding a reference to the WebControl project from the Web project. This should automatically show the controls in the toolbox.

Otherwise you can import the controls into the toolbox by adding a tab, then adding components via the DLL component picker.

All this is described in more detail in the help file under the Visual Studio configuration topic.


+++ Rick ---


I have a client who has had their wc controls disappear in VS. You can see them if you 'show all' but they are disabled, and we are getting the following message after adding them:

the following controls were successfully added to the toolbox but are not enabled in the active designer

The file extension for the active web page is .kjdp and the extension is included in tools/options/text editor/file extension as 'Web Forms Editor'. The path to the files is not particularly long and does not include spaces or weird characters.

If I add a new page with a wcsx extension, they appear properly. Should we even be using extensions for these page definitions, or does webconnect handle mappings in another way?







Michael
www.WebConnectionHosting.com

© 1996-2024