|
No, .Net 6 is not available for the .Net framework.
.Net 4.8 is the last version of the .Net framework.
And .Net 6 can not easily be used with VS2019, it is best to use VS2022.
|
|
|
|
|
Thanks
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
It's all .net, I don't care about branding. (And I'm using .net 4.8)
|
|
|
|
|
It's not just branding, between ".net framework" (say .net4.8) and ".net core" (say .net6) there are a few minor API incompatibilities that one can sometimes encounters...
|
|
|
|
|
That, and .NET 6 is cross-platform, allows the use of newer C# language features, and has a ton of performance improvements that will not be back-ported to .NET Framework.
|
|
|
|
|
|
That's like asking whether .NET Framework 4.8 is available for VB6.
.NET 6 is the latest released version of .NET, which grew out of .NET Core, which was placed as the successor to the .NET Framework. There are significant differences - for example, .NET Core and .NET are cross-platform, whereas .NET Framework was only available on Windows.
The last version of the .NET Framework is v4.8.1, which was released in August with a few minor improvements over 4.8:
Announcing .NET Framework 4.8.1 - .NET Blog[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
Yes, well, the very concept of "exceeds expectations" is insulting.
|
|
|
|
|
Not always. If someone goes way outside their assigned duties to take care of something that needs doing then they've exceeded expectations.
|
|
|
|
|
No, that's to be expected. The only way to exceed expectations is for the boss to have low expectations -- and that's insulting.
|
|
|
|
|
The expectations are for someone in your role, not for you personally.
|
|
|
|
|
There is an expectation that everyone be a decent human being -- even (shudder) a "team player".
|
|
|
|
|
Such a narrow view. I'm a CIO and when my staff goes above and beyond I work to ensure they're recognized and rewarded. I do NOT expect them to work 80 hour weeks - I expect them to work 40 and do the best they can, but when they go above and beyond this I notice, and so does the rest of the company.
The unfortunate truth about Dilbert is that far too many companies contribute to Scott Adams' materials.
|
|
|
|
|
obermd wrote: I do NOT expect them to work 80 hour weeks - I expect them to work 40 and do the best they can, but when they go above and beyond this I notice, and so does the rest of the company. This is the way
obermd wrote: The unfortunate truth about Dilbert is that far too many companies contribute to Scott Adams' materials. This is the truth
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
sort of like getting a C+
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
|
I'm working on a winforms desktop side-project in c#, it's for my internal project management, storing milestones and tasks, client notes, mcq quiz, etc., the idea is to open source it later.
I'm considering sqlite for database as it's the typical choice for standalone projects, isn't it? Another option is ms-access which works great but the caveat is that I don't have ms-office installed, I use LibreOffice instead. Is it possible to create and mange access databases (*.mdb) purely with ADO.NET code or do we need MSO installed? If not, what other database would you suggest for this kind of project?
|
|
|
|
|
Read the stuff at the top of the page: the Lounge is not for coding questions. Post it here instead: Ask a Question[^]
Ignoring the rules and annoying people you want free help from is not a good idea ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Hmm, that didn't strike me as a programming question, rather more of a "what tool should I use" question.
|
|
|
|
|
Sqlite is great, though personally I actually prefer the heavyweight champ SQL Express -- I have enough side projects in C# that it warrants using SQL Express with multiple DB's, and I don't have to worry about any nuances with Sqlite, though frankly the frameworks and libraries (Linq2Sql, EF, Dapper, FluentMigrator, etc) pretty much handle the nuances for me.
|
|
|
|
|
When I was using SQLite in a UWP app a few years ago, the main pain point was just that the style of database scheme project we normally used wasn't supported at all; and the closest match was apparently a non-idiomatic way to use the database and buggy as a result.
MS did fix the bug I found eventually (Achievement Unlocked), but not until a few years after the project had ended.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
For small projects, requiring a separate application be installed to manage data is a problem with moving from PC to PC. Even if you plan to use it only on 1 PC, eventually you'll need to migrate to a new machine. Having the data in 1 or more discrete files makes it easier. Since you're planning to open-source it, making the program and its data portable is critical.
I use MS Access for several small projects, as it fits the above criteria. Once you have a MDB built, all MDB interactions can be handled in code. Sadly, there are version problems between MS Office and the MS Access libraries, so getting that ironed out has been a PITA for me. But since you don't have MS Office, it shouldn't be a problem for you, but it could be for recipients. NOTE: If you don't have MS Access, you'll need to write a short program that constructs an MDB.
SQL Lite and SQL Express need to have tools installed, so those have to be installed and configured (probably no worse than MS Access). I don't know if the DB can be handled as a file, and included in an installer. I lack the knowledge to know if this is a problem.
LibreOffice? I assume LO Base has libraries that can be included in an installer, so this is a good option, as you can build the DBs in LO Base and can edit them as needed.
XML is also a good choice. The files are totally portable and learning to use it is not hard, although you'll probably want a separate file to represent each table.
I'm currently reconsidering my use of MS Access in a couple of personal projects, so answering your question has given me food for thought.
|
|
|
|
|
AFAIK the .MDB format is deprecated - .ACCDB is the new format.
I get your point about a single manageable file (although for any reasonably sized data set you are going to have to split the Access DB into multiple files to overcome the 2GB limit).
Personally I would just use LocalDB (SQL Server Express)
|
|
|
|
|
CHill60 wrote: AFAIK the .MDB format is deprecated - .ACCDB is the new format. You are correct -- "MDB" is long deprecated. I have the bad habit of typing "MDB" when I should by using "ACCDB". It may be that I'm just too lazy to type 2 extra characters ....
|
|
|
|