Closed sirmeili closed 7 years ago
Would public actually help -- or do you need public static? I can't imagine what your code looks like. Can you share a bit here so I can get a feel for your architecture?
Also, just in case you didn't see what I just posted on the HS forums (@dmurphy too):
- Long story short: YOU MAY HAVE TO UNINSTALL THE OLD PLUGIN AND INSTALL THE NEW PLUGIN TO CONTINUE GETTING UPDATES I thought I configured the original extension incorrectly in the Visual Studio marketplace, and Microsoft doesn't provide a way to change the setting I thought I messed up. So I removed the old extension from the gallery. That's why you get a 404 when you to go https://marketplace.visualstudio.com/items?itemName=thealexdresko.HomeSeerTemplates. The new location's forever home is at https://marketplace.visualstudio.com/items?itemName=thealexdresko.HomeSeerTemplates-18379 (arrrggg). I'm pretty frustrated by the whole experience and -- worse -- it doesn't even look like the setting makes a difference. I'm trying to automate publishing of the VSIX to the marketplace from the CI build, but I just don't think it's possible anymore.
Actually, I'm not sure. I'm not new to programming, but new to c#.net. I need to be able to access the HS object from another class (one that inherits the PageBuilder class). Even then, I'm not sure public static will help because it needs to be set after the connection to HS is made.
I see my mistake! I looked at the code at the B plugin was based off of and I see how it is done there :) I am going to close this. Sorry about the confusion.
10-4. Glad it worked out for you. Let me know if you run into any other problems.
I can't access the hs property outside of the plugin. I need this so I can break out my config pages into separate classes using the PageBuilder. Right now I can't access things like Hs.GetPageFooter()