Open musictopia2 opened 2 years ago
Are you referring to these libraries, which currently are at v. 6.0.1? If that's the case we can just roll them back.
Because the target framework is net6.0
Yes.
That should be fixed now
Thanks. Since I already did a fork, is there a way to get the changes on my end without having to delete my fork, the code then refork it?
Yea if you
Good news is i figured it out. The bad news is when I ran it, gave me a runtime error. First said failed to construct url. If I can have a screenshot of how it should look like, then I can try to see what changes to make to make it easier for others to be able to run and make it work. I assume could even be a database issue. Because if somebody does not have the same database as you do, that can cause issues. Unfortunately, it seems to be difficult to distribute applications that involve databases (especially sql server). With SQL Lite, if you commit the database ,then at least others can run and use it. However, I never have been able to make sql server work unless its only locally.
Here is a screenshot of the index page :) And a list of all the network calls
Regarding the database, yea MSSQL is not the easiest thing to get working if you do not know how to set it up. However, it's the database I use professionally, which is why I also use it for my personal projects
But testing how easy it is to switch to another database, would also be a great mini project and way to see if the interfaces need any changes.
Can you do a screenshot of the employer, work and invoice page. So I have some idea of what the UI contains
Sure:
For these pages, you will need to have created an employer, as otherwise the rest of the logic will not work. As seen [here](https://github.com/theodor349/Work-Tracker/blob/main/WorkTracker/Frontend/BlazorClient/Pages/Work.razor#:~:text=employers.First().Id).
I tried to run the webassembly project and it gets a runtime error. I think its because the newest version of the web assembly controls are used. I have the .net 6 but not the update to .net 6 installed. Do you think you can downgrade to 6.0 and not 6.0.1? Otherwise it if a person did not get the latest update to .net 6, then it won't work. I had the same issue on my projects. So I ended up not updating those files that would cause the problem.