AdvancedHMI Software
General Category => Support Questions => Topic started by: Archie on April 21, 2016, 01:41:19 PM
-
This is an issue with Visual Studio 2015 that seems to occur randomly. For me it has come and gone. I have reported to Microsoft as a bug. If you have also seen this same problem, please vote for it, so it can be brought to a higher level of attention. This is the link to the report:
https://connect.microsoft.com/VisualStudio/feedback/details/2606706/class-that-implements-icomponent-doesnt-always-show-in-toolbox
-
If you are having problems with this, the best solution is to use VS2013 until Microsoft can fix VS2015:
https://www.visualstudio.com/en-us/news/vs2013-community-vs.aspx
-
I am having this problem even when I open it in Visual Studio 2010. I have both 2010 and 2015 installed on my computer.
-
There seems to be a work around by adding any of the drivers to the form, then building the solution. This should make the rest of the drivers appear.
-
I just tried adding one and then a few drivers to the screen and then building, and it doesn't seem to be working for me.
-
Did you try exiting VS and reopening the project. If you are using VS2010, I can't really guarantee it will work because testing and support for that version has been dropped as of version 3.99e
-
Typical IT answer... "Have you tried turning it off and then back on again?"
Well, it worked. Thank you. I'm looking forward to testing this HMI.
-
UPDATE : Microsoft has acknowledged this bug and says it will be fixed in the next release of Visual Studio.
-
I had similar problems VS2015 but not with the drivers; my problem was the control components were missing. Rebooted and up they came!!
Running Windows 10.
-
I had this problem as well. I was able to reboot most of the drivers but I could not manage to pull up the DF1 driver which is the one i need. Im going to try VS2013.
-
YESSS!!!!!!!!!!!!!!!!!!!!!!!!!!
I found the driver DF1 Com in 3.99a with VS2015!
I could not figure out how to load 3.99 with VS2013. I am STOKED!!!!
-
The Df1Com driver has been renamed in the latest version to SerialDf1forSLCMicroCom
-
yeah. my issue wasnt that i just found out. i guess im having trouble connecting to the emulator. ill do some more research. any leads?
-
See if there is any help here:
http://advancedhmi.com/forum/index.php?topic=516.msg4427;topicseen#msg4427
-
that cleared everything up. I was using input addresses not memory addresses. Thank you Archie.
-
Did a quick test with Visual Studio 2017 and it seems this is resolved, at least on my PC.
-
Yes, It actually resolved in RC version, but I was terrified with 13GB download.
The new release now offers component options to install which is nice.