Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux will not accept search path #96

Open
oesolberg opened this issue Oct 26, 2018 · 9 comments
Open

Linux will not accept search path #96

oesolberg opened this issue Oct 26, 2018 · 9 comments
Assignees
Labels

Comments

@oesolberg
Copy link
Contributor

oesolberg commented Oct 26, 2018

Summary

Probing private path in linux does not handle backslash

Expected Behavior

When I use a plugin in Linux I expect it to use the probing path bin/

Current Behavior

Due to the probing path beeing written for Windows (with a backslash) Linux will not use it

Possible Solution

After testing I found that windows can accept backslash and slash, but Linux expects slash.
Fix output should also change the HSPI_<project>.exe.config file to use slash instead of backslash in probing privatePath

Same as issue #63
In this issue it is also shown in BLBackup config file
<probing privatePath="bin/BLBackup"/>

@alexdresko
Copy link
Owner

Fix incoming via d5fc9c7. It might take me a little bit to get a new version published because I want to get this working. I've been pestering Microsoft to create a CLI for publishing VS extensions for years now. They literally @'d me a couple weeks ago when they released the tool, so I'm kinda obligated. :)

Manually publishing the extension is one of the most annoying parts about working on this project, so I'm hoping this motivates me more.

@alexdresko alexdresko self-assigned this Oct 27, 2018
@alexdresko alexdresko added the bug label Oct 27, 2018
@alexdresko
Copy link
Owner

Welp, I automated the deployment, but I lost the marketplace ID I was using. :( Trying to get MS to fix it, but I might have to move everything to the new ID.

@alexdresko
Copy link
Owner

So I haven't heard from MS about my marketplace ID snafu. I have removed the old extension from the marketplace. You'll need to uninstall that version and reinstall this version: https://marketplace.visualstudio.com/items?itemName=thealexdresko.HomeSeerTemplates2

@alexdresko
Copy link
Owner

(Give it about an hour and an even newer release will be up)

@oesolberg
Copy link
Contributor Author

Sorry. I have not gotten around to test the latest version. Will try it soon(ish).

What "worries" me is that we are now going for .Net 4.7 and I don't think my test-machine (Win 2008 server) will support this version of .Net. Ah, but new is better etc - yes, I see that, but should we not keep up with the current .Net version of HomeSeer? Or am I just creating a lot of noise for nothing because I am not smart enough to see what is done in the HomeSeer extension?

@alexdresko
Copy link
Owner

Do you have 2008 R2 SP1? From what I can tell, 4.7.2 will run on that.

@alexdresko
Copy link
Owner

@oesolberg
Copy link
Contributor Author

oesolberg commented Nov 9, 2018

Thanks. I will look into it.
I hope Mono also supports it for running plugins in linux. I will test that as well.

@alexdresko
Copy link
Owner

My main reason for porting everything to .NET 4.7.2 is because that version is most compatible with .NET Standard 2.0. Ultimately, I want to convert the HSPI library (not the templates) to .NET Standard and create a set of .NET Standard templates. The whole point of .NET Standard is cross-platform support, so any plugin written in .NET Standard will work on linux. The only thing I'm not sure about yet is whether or not HS will load a .NET Standard plugin. That's something I hope to test before too much longer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants