Re: Access Application to Visual Studio

BTW, it is entirely possible, and not very difficult to do FTP with the .Net
platform. I have written several FTP clients using .Net. It's all about
sockets.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.

"Kevin Spencer" <kevin@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Op9WWI3PFHA.2584@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Jim,
>
> I do agree that this Access developer should probably stick with Access.
> Programming is a big step from using VBA to extend an existing app. When
> writing a program, the developer is responsible for every aspect of the
> program, not just the additional code that an Access developer adds on top
> of Access. That is, of course, why programmers make the big bucks. It
> takes years to master.
>
>> On a side note, I do take issue with the basic set of controls that are
>> included with Visual Studio .NET. A combobox in a grid, a masked edit
>> box,
>> and FTP support are pretty basic and should, in my opinion, be included.
>> How's this for a MasterCard moment: ComponentSpace FTP - $199. Developer
>> Express .NET Windows Forms Components Suite - $499. Incredibly happy
>> clients - priceless!
>
> I think you're looking at these "tools" in the wrong way. Again, as Visual
> Studio is a set of tools for creating applications of ANY kind, Microsoft
> only includes the bare bones of components that can be mixed and matched
> in any number of ways. Yes, pre-built components are nice, but Microsoft
> is the provider of the "parts," not the "cars."
>
> There are plenty of third-party companies out there that use Visual Studio
> and similar tools to build pre-made components. Some of these components
> can be very useful (in terms of productivity) when building certain types
> of apps. And these days, they are easy enough to find. Those products you
> mentioned are among them. Remember that Microsoft's Visual Studio is a
> tool set for ANY type of software development, including pre-built
> ready-made components. Microsoft is not in the business of creating such
> components (for the most part). They are in the business of providing
> tools, platforms, and applications that enable others to be more
> productive in their work. So, Microsoft doesn't generally include heavy,
> highly-specialized types of components in the Visual Studio package.
> Instead, they include small pieces of such components that can be used to
> build such components, for those companies that make money by selling such
> components.
>
> Think of it this way: You can buy a house. You can restore an existing
> house. But if you want to build a house, you don't buy a ready-made house.
> You buy lumber, nails, and the other components that make up a house, and
> you put them together yourself. Using Access is like buying, restoring or
> modifying an existing house. Using Visual Studio is for building houses
> (and any other types of buildings as well).
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> What You Seek Is What You Get.
>
>
> "Jim Rand" <jimrand@xxxxxxxxxxxxx> wrote in message
> news:OL$z532PFHA.1096@xxxxxxxxxxxxxxxxxxxxxxx
>> Kevin,
>>
>> That's the point. You have an Access developer who's looking at Visual
>> Studio.NET as a replacement. You know and I know that it's not. Daniel
>> is
>> trying to find some information to make a very basic decision - should he
>> migrate Access to VS.NET.
>>
>> There are pros and cons. On the plus side, you can do things in .NET
>> that
>> you can't in MS-Access. On the minus side, .NET is one of the most
>> challenging pieces of technology to master. If the Access solution meets
>> his needs, he should probably keep it. If it doesn't and he isn't
>> prepared
>> for an incredibly steep learning curve, he should probably just contract
>> the
>> project out to a .NET expert.
>>
>> On a side note, I do take issue with the basic set of controls that are
>> included with Visual Studio .NET. A combobox in a grid, a masked edit
>> box,
>> and FTP support are pretty basic and should, in my opinion, be included.
>> How's this for a MasterCard moment: ComponentSpace FTP - $199. Developer
>> Express .NET Windows Forms Components Suite - $499. Incredibly happy
>> clients - priceless!
>>
>> Jim
>>
>>
>
>


.

Relevant Pages

  • Re: Access Application to Visual Studio
    ... I do agree that this Access developer should probably stick with Access. ... Studio is a set of tools for creating applications of ANY kind, Microsoft ... There are plenty of third-party companies out there that use Visual Studio ... You can buy a house. ...
    (microsoft.public.vstudio.general)
  • Re: Best choice for developing?
    ... VSTO gives you the Access run-time, so you simply package your existing ... especially the specific point about the ADE. ... > Visual Studio Professional might not be the better option? ... >>>> a developer friend that I want MS Visual Studio, ...
    (microsoft.public.access.developers.toolkitode)
  • Re: VS.NET is too EXPENSIVE. Developers switching rapidly from it.
    ... > too much in light of the huge competition from Linux. ... If your company is considering a switch to Linux because you feel the cost ... of developer tools is too high then you may want to consider doing some more ... Visual Studio, as millions of developers do, then there is cost because ...
    (microsoft.public.vsnet.general)
  • Re: VS.NET is too EXPENSIVE. Developers switching rapidly from it.
    ... > too much in light of the huge competition from Linux. ... If your company is considering a switch to Linux because you feel the cost ... of developer tools is too high then you may want to consider doing some more ... Visual Studio, as millions of developers do, then there is cost because ...
    (comp.os.linux.misc)
  • Re: Can no longer publish my web site project
    ... another ftp client, CuteFtp, though. ... How do I go about attaching to another process? ... Open another copy of visual studio and attach it to the ... I am no longer able to publish a web site project using Visual Studio ...
    (microsoft.public.dotnet.framework.aspnet)
Loading