|
I'm opinionated, but in my defense, never made the claim to know it all.
|
|
|
|
|
I would suggest skipping. Net 7, and wait for. Net 8 which will be out in a few weeks. .Net 8 is a long term support (LTS) version and Microsoft will provide security patches for a longer period of time than. Net 7
|
|
|
|
|
VS 2022 does a check for package updates normally. It is very easy to set up local nuget_repo on either an internal server or local directory on dev PC. Nexus operates as a proxy service for nuget but probably a lot faster and easier to build your own proxy service copy from "public" sources to local machine.
|
|
|
|
|
I think where you are going in the wrong direction is to think that an "air-gapped dev system" is something bad, there "there is something wrong with that picture".
There are plenty of applications that work completely without the need for the Internet, for very valid reasons.
I did for example a few years back a data conversion job for a large nationwide client in the healthcare business. I actually had to work the other way around, I wrote and updated the conversion software on my own laptop, with no connection to the hospital's infrastructure (bar electricity). Initial test data was screened and anonymized before I got this on my computer. There was never one bit of live data on my system. And program changes were also transferred to the actual computer performing the conversion via read-only media. This way no patient data could possibly get out this way. Yes, a bit cumbersome, but workable.
And not that I really needed to Internet for any development, as the IDE/compiler/libraries work very nicely self-contained (it wasn't a Microsoft product).
I think it is an absolute fallacy these days that so many people think that everything is "in the cloud", "needs to be connected to the Internet". Beside that in some businesses, the air-gap exists is so that no data gets out of the environment. Hence for example the read-only media (DVD) that the OP mentioned.
And no, you ABSOLUTELY do not, NEVER, develop with any live data. NEVER EVER!
|
|
|
|
|
Ralf Quint wrote: I think where you are going in the wrong direction is to think that an "air-gapped dev system" is something bad, there "there is something wrong with that picture".
It's not that I think it's "wrong", it's that based on my experience with MS's development tools, they make your life kinda miserable if you are offline.
Ralf Quint wrote: I think it is an absolute fallacy these days that so many people think that everything is "in the cloud", "needs to be connected to the Internet".
I hope I didn't give the wrong impression--I'm entirely with you. I have a slow internet connection here at home, and I'm the guy who still, to this day, will always raise his hand and ask "how well will this work for those who are offline"...I despise products that assume you'll always be connected. I despise products that assume they'll be running on the fastest CPU with tons of memory and disk/network latency isn't a consideration, and they'll be the only products running on a system.
|
|
|
|
|
Well, this is one (of several) reasons why I do not use any MS development tools. Microsoft has completely lost touch with reality, and unfortunately, a lot of people just keep following anyway, like the lemmings...
|
|
|
|
|
Name one equivalent to VS - despite all its flaws.
I don't think anyone's being a lemming.
|
|
|
|
|
Define "equivalent to VS". And all the people that think that everything has to be on .NET and/or use VS, yes, they are lemmings. Or at least blind horses with blinders on.
I do all my development for years now (kind of always have) in Object Pascal and the Lazarus IDE (Delphi before that), which runs identically on Windows, Linux, macOS and then some.
Much less cruft than it comes with VS (or Eclipse, <shudder>), much more straight forward and much faster...
|
|
|
|
|
Yeah, you're new around here and don't know much about the types of developers that hang around here...
|
|
|
|
|
New around here? Nope, not really.
|
|
|
|
|
Barely over a year, yes, you're new.
The old timers around here tend to agree - this has been discussed many, many times over. As much as most hate VS, there's really no good replacement for it.
And I think you'll find that most developers here focus on Windows and .NET - specifically, C#. And they don't make the mistake of comparing apples with oranges.
Calling that bunch "lemmings" will make you rather unpopular, rather quickly around these parts.
|
|
|
|
|
dandy72 wrote: Barely over a year, yes, you're new.
Well, not sure where you got that info from, but you are certainly wrong. It's more likely around 7 or 8 years.
But anyway, if having a different opinion (and practical experience) isn't appreciated by some, oh well, so be it...
|
|
|
|
|
Ralf Quint wrote: Well, not sure where you got that info from, but you are certainly wrong. It's more likely around 7 or 8 years.
Have you changed profiles? Because yours says you've only been on since June 22 of last year.
Ralf Quint wrote: if having a different opinion (and practical experience) isn't appreciated by some, oh well, so be it..
It's not "having different opinion" that gets me, it's someone showing up on a very-much Windows/C#/.NET developer-centric web site, and calling VS users lemmings.
|
|
|
|
|
dandy72 wrote: Have you changed profiles? Because yours says you've only been on since June 22 of last year.
The oldest email from the CodeProject's "Daily News" here in my email folder is actually from 08/20/2009. I think I changed the email address once, but even that is several years ago, that's probably the 7 or 8 years that I mentioned before...
dandy72 wrote: It's not "having different opinion" that gets me, it's someone showing up on a very-much Windows/C#/.NET developer-centric web site, and calling VS users lemmings.
Please go back and see what the OP of this thread is about, programming offline. And that is something that VS is simply unsuited for. If someone insists on using it anyway, because that's the only tool (s)he knows, then I would consider the comparison to lemmings fitting...
|
|
|
|
|
My previous response included a link to the details of your profile (the "yours" in "because yours says[...]"
Ralf Quint wrote: If someone insists on using it anyway, because that's the only tool (s)he knows, then I would consider the comparison to lemmings fitting...
Now you're just being a child. VS has--literally--millions of users, and it's often the only tool that will work - for example - with the latest .NET release. You think people will forego its use just because it doesn't work offline as well as it could?
|
|
|
|
|
there is the visual studio 2022 installer that has to be installed first
then there is an option from that to save the files locally Create an offline installation - Visual Studio (Windows) | Microsoft Learn
then u need a 25GB DVD split to make it readonly
then u need to copy to a test env and test the install (meaning test all you know and want of functions and coding a dummy project) (switch off and disable task scheduled and web checking)
then install in dev prod env
nuget part you need to do your rnd and get the offline packs etc (NuGet Server Local?
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
I'm well aware of the process, having done it for a number of years. My questions were more along the lines of 1) how 2022 behaves offline, 2) how hard is it, based on your experience, to set up a local NuGet server, and 3) how well does 2022 play with an offline local NuGet server.
Be wary of strong drink. It can make you shoot at tax collectors - and miss.
Lazarus Long, "Time Enough For Love" by Robert A. Heinlein
|
|
|
|
|
well you do have to test it know how it behaves ...the best way is to get a heavy NuGet packaged project from say github and make it offline (via a newget server running locally) and test it for windows forms and normally back in the day projects i don't see much issues speaking from understanding.. but what works on my machine may not on yours.....i havent set up local nuget etc..
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
I'm paranoid but I see no reason not to dedicate one PC to the internet (as a proxy) and then RDP into it to see what is what. At some point, someone assumes responsibility for something.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
That RDP connection violates the inviolable "air-gap" requirement. The point of responsibility is me; I assume the responsibility for what I put on the DVDs that are transferred. Deities help me if I introduce a virus that destroys anything on the internal network. At least with the air-gap, I am protected from data egress.
Be wary of strong drink. It can make you shoot at tax collectors - and miss.
Lazarus Long, "Time Enough For Love" by Robert A. Heinlein
|
|
|
|
|
Wifi and Bluetooth go over the air. RDP is a one way wire with a screen.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
That's being pedantic over the meaning of the phrase "air-gap". The accepted usage in computer-speak is no network connectivity of any kind, over any variety of medium, hard-wire or over-the-air. There is a conceptual physical gap surrounding the network.
Be wary of strong drink. It can make you shoot at tax collectors - and miss.
Lazarus Long, "Time Enough For Love" by Robert A. Heinlein
|
|
|
|
|
Quote: RDP is a one way wire with a screen.
RDP is one of the most exploited protocols out there. Because it is everything but one way. For example, you can set up printing to a local printer, which, if this mere possibility is exploited and abused, is one way of data egress...
|
|
|
|
|
Can't give much advice on air-gapped development, but we use the free and open-source version of Gitea as a local Git server on Windows for years now which works very well. Gitea can function as a NuGet server and also has support for Cargo, Chef, Composer, Conan, Conda, Container, Helm, Maven, npm, Pub, PyPI, RubyGems, Vagrant, etc.
Github - Gitea[^]
|
|
|
|
|
Very helpful, thank you! We have GitLab Enterprise running on the internal network; it can be my local NuGet server. Then all I have to do it make sure I download all the packages I need and stuff them up there.
Be wary of strong drink. It can make you shoot at tax collectors - and miss.
Lazarus Long, "Time Enough For Love" by Robert A. Heinlein
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
