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

Document and Update solution files #157

Open
AndrewCook opened this issue Aug 25, 2020 · 5 comments
Open

Document and Update solution files #157

AndrewCook opened this issue Aug 25, 2020 · 5 comments
Assignees

Comments

@AndrewCook
Copy link

In July 2020 getting small basic's source code to run on a new contributor's machine was a cumbersome process. This should be improved with updates to source code and documentation that clearly states what is needed as well as working to automate away as many steps as possible that a contributor needs to complete to have the source code running on their machine.

@nonkit
Copy link
Member

nonkit commented Aug 26, 2020

@AndrewCook, I've written an article in TechNet Wiki. Does following article help this issue especially for documentation?
Microsoft Small Basic Online v1.0: How to Build

@AndrewCook
Copy link
Author

@nonkit That does help. 👍 I'm also planning on adding similar documentation to the README of this repo to improve discoverability.

@nonkit
Copy link
Member

nonkit commented Sep 2, 2020

@AndrewCook, good idea!

@Youssef1313
Copy link

Hi @AndrewCook!
I came to this repository by chance, and I'm willing to contribute.
For me, opening the solution was very straightforward. Just did a dotnet restore, then opened the sln file in Visual Studio. Then, just set SmallBasic.Editor as the startup project. After that, just a build & run (which will automatically restore npm packages for SmallBasic.Client). Finally, it should work. The npm restore still haven't finished yet at the time of writing this (it takes a while due to relatively slow internet connection). I'll update the comment after the npm restore finishes. But I'm expecting everything to work just fine.

Can you elaborate more on what can make this process cumbersome?

@Youssef1313
Copy link

Ok I actually got rzc discover exited with code 1.

I'm not sure of its cause.

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

No branches or pull requests

3 participants