It's an absolute mess. After years of complaining about the lack of SSRS support in MVC, then in .NET Core, and now in .NET, Microsoft's official response[^] is that you have to pay for PowerBI Premium, and move all of your reports to their portal.
There are some free third-party libraries which provide limited SSRS support - for example:
lkosson/reportviewercore[^] - No interactive web control for previewing or entering parameters; no SQL Spatial types support; workaround required for image support on Linux;
We are in the process of developing an online permitting application that collects data and allows the client to make payment(s). I have been tasked with determining what the best option(s)/version(s) are for UI and backend development.
I am a novice and am not very familiar with any of these newer technologies.
Any suggestions for best resources for seeking guidance would be appreciated. If thisis not the proper forum for such a request, please advise.
.NET Core 2.x is out of support, and should not be used - support for 2.2 ended in December 2019.
The same goes for .NET 5 - support ended in May last year.
If you decide to go with .NET, your choices are:
.NET 6 - The current "long-term support" release, supported until November 2024;
.NET 7 - The current "short-term support" release, supported until May 2024;
.NET 8 - Due to be released in November 2023, this will be the next LTS release;
NB: "Support" in this case means actively receiving security patches. The out-of-support versions will still work, but they may contain security vulnerabilities which will remain unpatched. It's always best to keep your application up-to-date, and updates tend to be reasonably easy.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Most folks on here are going to suggest a Microsoft solution. But, I won't. Muwahahaha.
This is a very open ended discussion that could go on for weeks. But, if you're a novice that's just overkill and will only kill the vibe. Start with a minimal framework and eventually learn how it works under the hood. Emphasis on minimal. So many web developers think they're web developers but they have no idea how React works under the hood for instance.
Udemy has several courses on it, etc. too. Eventually, you'll want to learn proper relational DB design, etc. but save that for later. Because you'll have a lot to learn right now, including polyfills, ponyfills, browser quirks, accessibility, etc.
Note: Stay far, far away from Angular if you want to be a good web developer.
You would not choose min(300px, 500px), as that makes no sense: 300 is always smaller than 500. It is used when you want to select the smallest of a set of different value types. See the example at CSS min() function[^], which will select either 50% of the width of the div element, or 300 pixels if that is smaller. So the selected element will not be larger than 300 pixels wide.
The reason you got downvoted most likely is that you asked for a lot of work in the reply (real world code examples), but you didn't put a great amount of effort into the question yourself. Remember, we're happy to help but nobody here works for free. Our time is also valuable.
That being said, the most common reason people need to deal with a minimum value of anything in web development is with responsiveness and scaling as a result of it. The browser (and thus viewport) can be resized when using a desktop computer. If the user sizes the browser too small, sometimes you need a guarantee an element/container maintains at least a certain size. Or maybe you want to scale down font size with a smaller viewport while ensuring it doesn't get too small, etc. Whatever the case, responsiveness is the usual reason they are used.
The max size is used less in practice. But sometimes it can useful when going in the opposite direction and making sure things don't scale too large, if say the user is on an 8K display, etc.
I am creating a User registration form using React JS and as I have defined the fields and its validations along with the submit handler, it does not console log Hello World after pressing submit button. It doesn't seem to function at all. I am sharing my code below:
I'm testing sciter (very impressed so far!) for a wrapper around a local intranet web page.
The intranet page's ssl certificate (https://intranet.local) is signed with the local Windows CA; the CA's root certificate is installed in Windows.
When I open the intranet page in Firefox etc. the site's certificate is accepted just fine.
Using scapp.exe with main.html <iframe src="https://intranet.local/"></iframe> it complains about the cerificate and even accepting the cert does not work.
Anything I can do here?
You may have noticed this is a forum for web development. It sounds like you're having issues with a third-party application. If this is what you're referring to, then you may have better luck posting your question in the article's comments.
It could be that this app, scapp.exe, is within a different environment. For instance, you can use curl on Windows, but that doesn't mean it'll use the Windows CA store by default. But again, you'd have better luck asking for help with the author of the application and/or support for the application, rather than asking a general web development forum for help.
thanks for your reply.
Actually, scapp.exe is from the sciter examples itself as referred at https://sciter.com/scapp/
"ScApp – standalone Sciter executable". Sorry for not mentioning that. I suppose it's not a third party app?
What forum do you suggest I can ask for help here?