@doctordns Maybe, starting a new open source project could help? I also contacted @jongalloway before build. He told me, he would come with more news after build. But no new news yet. I know he is the only one that's working on the project. But he could maybe add some leads. So the project gets alive again... Other option is starting a new open source project...
@SvenVandenbrande @doctordns personally, I don't think forking the project is the correct approach. OpenLiveWriter was created with the intention of being a community driven project, and I agree that this doesn't seem to have happened. What I think does need to happen is that we need to empower people (like yourselves) who are interested in helping/owning the project, and to let them run with it. That will mean handing over some control, but that is far better than letting the project dwindle.
I would love to hear @jongalloway and @shanselman and @onovotny thoughts on this from a .Net Foundation perspective.
Would there be any issues with adding more people into the OpenLiveWriter GitHub repo with the ability to commit code changes, and push out new versions?
And indeed it would be a good idea to empower people for this
@SvenVandenbrande there are definiltey discussions to be had in this area in terms of technology choice, etc. I would say though that a lot of people like using OpenLiveWriter as it is. Yes, it might not be using the most up to date technologies, but it works, and it is good at what it done. Making wholesale chanegs to the application and it's underlying technologies would need to be done carefully. I would rather see any existing bugs in the application corrected and pushed out with new versions. This is much easier to do, and to get people up to speed with how things are done, and again empowering them to do it, and once that community base is established, further changes/improvements can be discussed, as everyone will have a better idea about what is required.
Just my two cents
I don't have any active involvement in this project, I am just an interested 3rd party :-D
I'm sure anyone interested in stepping up would be welcome
I don't monitor gitter, only noticed this because you tagged me
@SvenVandenbrande in all honesty, I am not sure, I am not familiar with the code base. The point that I was trying to make was that I would be hesitant to jump to another technology, given that there is an existing, working, application that has a number of bugs and feature requests associated with it. There is nothing to say that anything will be any easier on a different technology stack.
Hello :) Is anyone looking at the OpenLiveWriter.github.io issues? https://github.com/OpenLiveWriter/OpenLiveWriter.Github.io
Can someone please help me on how to left intend in the title post bar in Open live writer?
I am trying to build the installer but it's missing from the nuget package (?)
I've been trying this as well. And I didn't have to do that. The post build project runs a batch script that has all the paths in it. It puts the installer into the releases folder. I have changed the build to work with Visual Studio 2017 though. I also had to change the version.txt file to have a higher version number otherwise squirrel fails with a file not found exception.
As @JimGalasyn mentions, here is the GitHub issue that people can follow if interested: OpenLiveWriter/OpenLiveWriter#787
I have noticed something else that won't work during the publish, and I am trying to get the build to run on my machine, but I am running into this error:
Did you run into something similar?
If so, how did you get around it?
Does it correctly find/use the VSSetup PowerShell cmdlet ?
It tells me "In order to run this tool you need either Visual Studio 2015 or Microsoft Build Tools 2015 tools installed" and sends me to a defunct link -- why they no use redirect? :D VS generally does side-by-side installations well, but still I'd rather not install VS2015 stuff with my VS2019 bits.