Welcome to the Lounge

dandy7226-Oct-23 3:00

26-Oct-23 3:00

Name one equivalent to VS - despite all its flaws.

I don't think anyone's being a lemming.

Ralf Quint27-Oct-23 9:32

27-Oct-23 9:32

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...

dandy7228-Oct-23 8:07

28-Oct-23 8:07

Yeah, you're new around here and don't know much about the types of developers that hang around here...

Ralf Quint29-Oct-23 13:44

29-Oct-23 13:44

New around here? Nope, not really.

dandy7230-Oct-23 4:25

30-Oct-23 4:25

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.

Ralf Quint30-Oct-23 5:06

30-Oct-23 5:06

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...

dandy7230-Oct-23 5:48

30-Oct-23 5:48

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.

Ralf Quint30-Oct-23 8:45

30-Oct-23 8:45

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...

dandy7230-Oct-23 9:46

30-Oct-23 9:46

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?

abmv17-Oct-23 4:47

abmv

17-Oct-23 4:47

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

JudyL_MD17-Oct-23 4:54

17-Oct-23 4:54

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

abmv17-Oct-23 5:04

abmv

17-Oct-23 5:04

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

Gerry Schmitz17-Oct-23 5:19

Gerry Schmitz

17-Oct-23 5:19

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

JudyL_MD17-Oct-23 6:10

17-Oct-23 6:10

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

Gerry Schmitz17-Oct-23 9:14

Gerry Schmitz

17-Oct-23 9:14

Wifi and Bluetooth go over the air. RDP is a one way wire with a screen.

JudyL_MD17-Oct-23 10:21

17-Oct-23 10:21

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

Ralf Quint18-Oct-23 10:51

18-Oct-23 10:51

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...

RickZeeland17-Oct-23 7:25

RickZeeland

17-Oct-23 7:25

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[^]

JudyL_MD17-Oct-23 7:35

17-Oct-23 7:35

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

robertburgh18-Oct-23 2:29

robertburgh

18-Oct-23 2:29

After reading all the replies, just one additional note: .Net 7 isn't LTS. Use .NET 6 or wait for .NET 8.

The is assuming that LTS support is important for your environment.

S Ravi Kumar (TechieRathore)

S Ravi Kumar (TechieRathore)18-Oct-23 3:22

18-Oct-23 3:22

For first part of your question, I don't have an answer like other people as I have never experienced using Visual Studio in offline mode. Regarding the Second part about setting up local Nuget Server, I would say it's moderately easy to do following the documentations, I had done it once in one of my previous organisations where we had some internal company specific nuget packages.

Steve Naidamast18-Oct-23 5:03

Steve Naidamast

18-Oct-23 5:03

I have both Visual Studio 2019 and 2022 installed on my development machine.

For my current development efforts, which is military simulations development, I find VS 2019 with .NET Framework 4.6 works just fine.

With the little I have done with Visual Studio 2022 I have yet to see any problems. But, then again I have not used it extensively.

Since you appear to be working in the same technical areas that I am in terms of the needed technologies, I don't see any reason for you to upgrade to Visual Studio 2022 unless you want the latest features and want to work with .NET Core 6.x and above

Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com

jsrjsr18-Oct-23 12:55

jsrjsr

18-Oct-23 12:55

We use VS2019 and VS2022 on VMs running on a system that is firewalled off from just about everything. For NuGet packages we download them and transfer them to a server that is inside the firewall. The NuGet packages are in a folder that is shared to the VMs. It's irritating to update VS and the NuGet packages, but it works.

AU_Steve18-Oct-23 17:05

AU_Steve

18-Oct-23 17:05

I've not used VS2022 offline so I can't comment on whether it works fine or not.

If you want to use .Net6+ then you need to use VS2022. It is an improvement over VS2019, especially with Git.

As for Nuget, you don't need a dedicated "Nuget application server" as such, you can just use a regular folder as a Nuget package source, either on the same machine or a shared network drive. VS2019/20 is happy to find and install packages from a plain windows folder. You just wont get some of the extra meta data that a Nuget server adds.