Looking for your highly subjective opinions (from those of you who have been
working extensively with VS 2005).
I have a client that needs/wants a complete rewrite of an existing
application. I will be proposing a .NET Windows application with a
supporting SQL Server database. It will likely take 4-5 months before we
roll out the first production version.
Because of the apparent issues with VS 2005 (poor performance, unpredictable
and generally buggy behaviour), I am thinking it might make sense to develop
this app in VS.NET 2003/.NET 1.1. Then, around the time we're ready to roll
out the first production version, migrate it to .NET 2.x just before going
live.
I say 2.x because Microsoft has plans to release a service pack for it
mid-way through 2006, so we might have a minor version number change at that
time. Also, it appears that the service pack from Microsoft, if released
mid-year, will stabilize things so we can [hopefully] have a smooth
transition to 2.x just before going live.
Does this strategy make sense? Thoughts? Opinions?
Thanks! 12 1501
Jeff wrote: Looking for your highly subjective opinions (from those of you who have been working extensively with VS 2005).
I have a client that needs/wants a complete rewrite of an existing application. I will be proposing a .NET Windows application with a supporting SQL Server database. It will likely take 4-5 months before we roll out the first production version.
Because of the apparent issues with VS 2005 (poor performance, unpredictable and generally buggy behaviour), I am thinking it might make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around the time we're ready to roll out the first production version, migrate it to .NET 2.x just before going live.
I say 2.x because Microsoft has plans to release a service pack for it mid-way through 2006, so we might have a minor version number change at that time. Also, it appears that the service pack from Microsoft, if released mid-year, will stabilize things so we can [hopefully] have a smooth transition to 2.x just before going live.
Does this strategy make sense? Thoughts? Opinions?
Thanks!
This makes some sense, however doing something in this fashion is not
recommended as some things may go haywire during the conversion process
that you would need to fix. I find it easier just to deal with VS 2005
and make it with .NET 2.0 to start.
Not only that, but you are pretty much going to miss out on a good
amount of functionality which VS.NET 2005 provides.
Have you actually tried it? I ask because you say apparent...
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Stefan Nuxoll" <ne******@gmail .com> wrote in message
news:11******** *****@corp.supe rnews.com... Jeff wrote: Looking for your highly subjective opinions (from those of you who have been working extensively with VS 2005).
I have a client that needs/wants a complete rewrite of an existing application. I will be proposing a .NET Windows application with a supporting SQL Server database. It will likely take 4-5 months before we roll out the first production version.
Because of the apparent issues with VS 2005 (poor performance, unpredictable and generally buggy behaviour), I am thinking it might make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around the time we're ready to roll out the first production version, migrate it to .NET 2.x just before going live.
I say 2.x because Microsoft has plans to release a service pack for it mid-way through 2006, so we might have a minor version number change at that time. Also, it appears that the service pack from Microsoft, if released mid-year, will stabilize things so we can [hopefully] have a smooth transition to 2.x just before going live.
Does this strategy make sense? Thoughts? Opinions?
Thanks! This makes some sense, however doing something in this fashion is not recommended as some things may go haywire during the conversion process that you would need to fix. I find it easier just to deal with VS 2005 and make it with .NET 2.0 to start.
RE:
<< Have you actually tried it?... >>
No, because I have work to do. And no, I'm not flaming or being negative.
I'm a *huge* fan of Microsoft. I also have a lot of time constraints and
simply don't have the time to screw around with a product which, given all
of the chatter in the varous Microsoft NGs, was apparently rushed to market
(or at least not fully developed when released). It appears that one one
must be willing to deal with slow performance, random "freezing", machine
crashes, etc. Given the volume of reports I think it's reasonable to
conclude that I would likely experience similar symptoms.
So while I'm looking to play it safe I also don't want to be obviously and
unnecessarily cautious. So I guess I'd be swayed to go with VS 2005 right
away if a number of people responded to my post here claiming that they were
totaly happy with VS 2005 and that they *never* experience any of the
frequently reported "buggy" behaviour.
-Jeff
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c om> wrote in
message news:up******** ******@tk2msftn gp13.phx.gbl... Not only that, but you are pretty much going to miss out on a good amount of functionality which VS.NET 2005 provides.
Have you actually tried it? I ask because you say apparent...
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard. caspershouse.co m
"Stefan Nuxoll" <ne******@gmail .com> wrote in message news:11******** *****@corp.supe rnews.com... Jeff wrote: Looking for your highly subjective opinions (from those of you who have been working extensively with VS 2005).
I have a client that needs/wants a complete rewrite of an existing application. I will be proposing a .NET Windows application with a supporting SQL Server database. It will likely take 4-5 months before we roll out the first production version.
Because of the apparent issues with VS 2005 (poor performance, unpredictable and generally buggy behaviour), I am thinking it might make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around the time we're ready to roll out the first production version, migrate it to .NET 2.x just before going live.
I say 2.x because Microsoft has plans to release a service pack for it mid-way through 2006, so we might have a minor version number change at that time. Also, it appears that the service pack from Microsoft, if released mid-year, will stabilize things so we can [hopefully] have a smooth transition to 2.x just before going live.
Does this strategy make sense? Thoughts? Opinions?
Thanks! This makes some sense, however doing something in this fashion is not recommended as some things may go haywire during the conversion process that you would need to fix. I find it easier just to deal with VS 2005 and make it with .NET 2.0 to start.
Well, I'm not gonna give you the free lunch you seek (you have to try
VS2005 out for yourself), but I can say that the bugs I have run into are
worth it for the many benefits that VS2005 brings.
It's not our job to "sway" you... I'm sure there are people still using VS6
because there are too many bugs in subsequent releases, but it is their
choice... It's more of a cost/benefit analysis you have to do according to
your own values/tolerance/etc...
For example, just yesterday I fixed a long-standing layout bug in one of our
aspx pages just because of the collapsible tags in the VS2005 HTML editor.
The collapsible tags feature, in conjunction with the new integrated HTML
code formatter, allowed me to greatly simplify how the HTML was displayed,
making the syntax error very simple to catch. This was an error that I had
spent searching for at least a full day with VS2003... But the VS2005 came
with some bugs, including some pretty big ones when it comes to deployment
of web sites and also a very annoying bug in which VS2005 checks into source
control files under the /bin directory when clearly, nothing in that folder
should be checked into source control. Is it worth the upgrade?
Absolutely, even through there are bugs, the benefits hugely outweight the
annoyances for me.
You have to make a similar evaluation and decision, based on your needs.
"Jeff" <A@B.COM> wrote in message
news:O4******** ******@TK2MSFTN GP12.phx.gbl... RE: << Have you actually tried it?... >>
No, because I have work to do. And no, I'm not flaming or being negative. I'm a *huge* fan of Microsoft. I also have a lot of time constraints and simply don't have the time to screw around with a product which, given all of the chatter in the varous Microsoft NGs, was apparently rushed to market (or at least not fully developed when released). It appears that one one must be willing to deal with slow performance, random "freezing", machine crashes, etc. Given the volume of reports I think it's reasonable to conclude that I would likely experience similar symptoms.
So while I'm looking to play it safe I also don't want to be obviously and unnecessarily cautious. So I guess I'd be swayed to go with VS 2005 right away if a number of people responded to my post here claiming that they were totaly happy with VS 2005 and that they *never* experience any of the frequently reported "buggy" behaviour.
-Jeff
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c om> wrote in message news:up******** ******@tk2msftn gp13.phx.gbl... Not only that, but you are pretty much going to miss out on a good amount of functionality which VS.NET 2005 provides.
Have you actually tried it? I ask because you say apparent...
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard. caspershouse.co m
"Stefan Nuxoll" <ne******@gmail .com> wrote in message news:11******** *****@corp.supe rnews.com... Jeff wrote: Looking for your highly subjective opinions (from those of you who have been working extensively with VS 2005).
I have a client that needs/wants a complete rewrite of an existing application. I will be proposing a .NET Windows application with a supporting SQL Server database. It will likely take 4-5 months before we roll out the first production version.
Because of the apparent issues with VS 2005 (poor performance, unpredictable and generally buggy behaviour), I am thinking it might make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around the time we're ready to roll out the first production version, migrate it to .NET 2.x just before going live.
I say 2.x because Microsoft has plans to release a service pack for it mid-way through 2006, so we might have a minor version number change at that time. Also, it appears that the service pack from Microsoft, if released mid-year, will stabilize things so we can [hopefully] have a smooth transition to 2.x just before going live.
Does this strategy make sense? Thoughts? Opinions?
Thanks! This makes some sense, however doing something in this fashion is not recommended as some things may go haywire during the conversion process that you would need to fix. I find it easier just to deal with VS 2005 and make it with .NET 2.0 to start.
Re:
<< It's not our job to "sway" you >>
Well, yes, of course not. But I'm looking to learn from some of you who have
*not* been complaining. Maybe you have not observed the bugs - maybe you
just aren't saying anything.
"Gabriel Magana" <no***@nospam.c om> wrote in message
news:OA******** ******@TK2MSFTN GP09.phx.gbl... Well, I'm not gonna give you the free lunch you seek (you have to try VS2005 out for yourself), but I can say that the bugs I have run into are worth it for the many benefits that VS2005 brings.
It's not our job to "sway" you... I'm sure there are people still using VS6 because there are too many bugs in subsequent releases, but it is their choice... It's more of a cost/benefit analysis you have to do according to your own values/tolerance/etc...
For example, just yesterday I fixed a long-standing layout bug in one of our aspx pages just because of the collapsible tags in the VS2005 HTML editor. The collapsible tags feature, in conjunction with the new integrated HTML code formatter, allowed me to greatly simplify how the HTML was displayed, making the syntax error very simple to catch. This was an error that I had spent searching for at least a full day with VS2003... But the VS2005 came with some bugs, including some pretty big ones when it comes to deployment of web sites and also a very annoying bug in which VS2005 checks into source control files under the /bin directory when clearly, nothing in that folder should be checked into source control. Is it worth the upgrade? Absolutely, even through there are bugs, the benefits hugely outweight the annoyances for me.
You have to make a similar evaluation and decision, based on your needs.
"Jeff" <A@B.COM> wrote in message news:O4******** ******@TK2MSFTN GP12.phx.gbl... RE: << Have you actually tried it?... >>
No, because I have work to do. And no, I'm not flaming or being negative. I'm a *huge* fan of Microsoft. I also have a lot of time constraints and simply don't have the time to screw around with a product which, given all of the chatter in the varous Microsoft NGs, was apparently rushed to market (or at least not fully developed when released). It appears that one one must be willing to deal with slow performance, random "freezing", machine crashes, etc. Given the volume of reports I think it's reasonable to conclude that I would likely experience similar symptoms.
So while I'm looking to play it safe I also don't want to be obviously and unnecessarily cautious. So I guess I'd be swayed to go with VS 2005 right away if a number of people responded to my post here claiming that they were totaly happy with VS 2005 and that they *never* experience any of the frequently reported "buggy" behaviour.
-Jeff
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c om> wrote in message news:up******** ******@tk2msftn gp13.phx.gbl... Not only that, but you are pretty much going to miss out on a good amount of functionality which VS.NET 2005 provides.
Have you actually tried it? I ask because you say apparent...
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard. caspershouse.co m
"Stefan Nuxoll" <ne******@gmail .com> wrote in message news:11******** *****@corp.supe rnews.com... Jeff wrote: > Looking for your highly subjective opinions (from those of you who > have been working extensively with VS 2005). > > I have a client that needs/wants a complete rewrite of an existing > application. I will be proposing a .NET Windows application with a > supporting SQL Server database. It will likely take 4-5 months before > we roll out the first production version. > > Because of the apparent issues with VS 2005 (poor performance, > unpredictable and generally buggy behaviour), I am thinking it might > make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around > the time we're ready to roll out the first production version, migrate > it to .NET 2.x just before going live. > > I say 2.x because Microsoft has plans to release a service pack for it > mid-way through 2006, so we might have a minor version number change > at that time. Also, it appears that the service pack from Microsoft, > if released mid-year, will stabilize things so we can [hopefully] have > a smooth transition to 2.x just before going live. > > Does this strategy make sense? Thoughts? Opinions? > > Thanks! This makes some sense, however doing something in this fashion is not recommended as some things may go haywire during the conversion process that you would need to fix. I find it easier just to deal with VS 2005 and make it with .NET 2.0 to start.
Jeff <A@B.COM> wrote: Looking for your highly subjective opinions (from those of you who have been working extensively with VS 2005).
I have a client that needs/wants a complete rewrite of an existing application. I will be proposing a .NET Windows application with a supporting SQL Server database. It will likely take 4-5 months before we roll out the first production version.
Because of the apparent issues with VS 2005 (poor performance, unpredictable and generally buggy behaviour), I am thinking it might make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around the time we're ready to roll out the first production version, migrate it to .NET 2.x just before going live.
That sounds like a very bad idea to me. At the very least you should be
trying to run all your code on a box which only has 2.0 whenever you
run tests. There are quite a few tiny breaking changes which may well
not affect you - but just might...
You should always try to test in as close to the real environment as
posisble.
--
Jon Skeet - <sk***@pobox.co m> http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
>> and that they *never* experience any of the frequently reported "buggy" behaviour.
Never? Really! I guess you intend to be waiting a long time.
On a more helpful note ... I see your point.
But, Stefan makes a good observation too. If you are really concerned &
decide to be cautious, you could probably be embrace something like xUnit
tests That way you could reduce the inherent risk that Stefan calls out.
Personally for me, VS.NET 2005 has been worth the hassles of switching.
--
Naraendira Kumar R.R.
~~~~~~~~~~~~~~~ ~~~~~~~~~~~~
"Jeff" <A@B.COM> wrote in message
news:O4******** ******@TK2MSFTN GP12.phx.gbl... RE: << Have you actually tried it?... >>
No, because I have work to do. And no, I'm not flaming or being negative. I'm a *huge* fan of Microsoft. I also have a lot of time constraints and simply don't have the time to screw around with a product which, given all of the chatter in the varous Microsoft NGs, was apparently rushed to market (or at least not fully developed when released). It appears that one one must be willing to deal with slow performance, random "freezing", machine crashes, etc. Given the volume of reports I think it's reasonable to conclude that I would likely experience similar symptoms.
So while I'm looking to play it safe I also don't want to be obviously and unnecessarily cautious. So I guess I'd be swayed to go with VS 2005 right away if a number of people responded to my post here claiming that they were totaly happy with VS 2005 and that they *never* experience any of the frequently reported "buggy" behaviour.
-Jeff
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c om> wrote in message news:up******** ******@tk2msftn gp13.phx.gbl... Not only that, but you are pretty much going to miss out on a good amount of functionality which VS.NET 2005 provides.
Have you actually tried it? I ask because you say apparent...
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard. caspershouse.co m
"Stefan Nuxoll" <ne******@gmail .com> wrote in message news:11******** *****@corp.supe rnews.com... Jeff wrote: Looking for your highly subjective opinions (from those of you who have been working extensively with VS 2005).
I have a client that needs/wants a complete rewrite of an existing application. I will be proposing a .NET Windows application with a supporting SQL Server database. It will likely take 4-5 months before we roll out the first production version.
Because of the apparent issues with VS 2005 (poor performance, unpredictable and generally buggy behaviour), I am thinking it might make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around the time we're ready to roll out the first production version, migrate it to .NET 2.x just before going live.
I say 2.x because Microsoft has plans to release a service pack for it mid-way through 2006, so we might have a minor version number change at that time. Also, it appears that the service pack from Microsoft, if released mid-year, will stabilize things so we can [hopefully] have a smooth transition to 2.x just before going live.
Does this strategy make sense? Thoughts? Opinions?
Thanks! This makes some sense, however doing something in this fashion is not recommended as some things may go haywire during the conversion process that you would need to fix. I find it easier just to deal with VS 2005 and make it with .NET 2.0 to start.
Did you know that Microsoft did not issue a single service pack for VS 2003?
Did you know that even hot fixes required you to call Microsoft ($250 to
talk to an engineer) to be able to get the hot fixes? What makes you think
that VS 2003 has any less bugs than VS 2005?
My experience with VS 2005 has been a good one so far, its an incredible
developers tool much better than 2003 and worth every penny in my opinion.
Yes, it does have its problems, some very annoying but not more or less than
what VS 2003 has in my opinion. If I was you, I would workaround any
problems that VS 2005 and develop my product with VS 2005.
"Jeff" <A@B.COM> wrote in message
news:es******** ******@TK2MSFTN GP11.phx.gbl... Looking for your highly subjective opinions (from those of you who have been working extensively with VS 2005).
I have a client that needs/wants a complete rewrite of an existing application. I will be proposing a .NET Windows application with a supporting SQL Server database. It will likely take 4-5 months before we roll out the first production version.
Because of the apparent issues with VS 2005 (poor performance, unpredictable and generally buggy behaviour), I am thinking it might make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around the time we're ready to roll out the first production version, migrate it to .NET 2.x just before going live.
I say 2.x because Microsoft has plans to release a service pack for it mid-way through 2006, so we might have a minor version number change at that time. Also, it appears that the service pack from Microsoft, if released mid-year, will stabilize things so we can [hopefully] have a smooth transition to 2.x just before going live.
Does this strategy make sense? Thoughts? Opinions?
Thanks!
Hi Jeff,
I've been using VS.Net 2005 for about a year now, since beta 1 I believe.
Beta versions had certain bugs in them, but were essentially stable. I have
never experienced any performance problems with it. I believe most of the
perceived performance problems were due to issues related to the uninstall
of previous beta versions. The upgrade process to the next beta (and finally
to the release version) has been highly complex, involving separate
uninstalls of various components in a certain order prior to installing the
newer version. If these procedures were not followed exactly, problems
occurred. Some of these problems manifested themselves as slow performance.
I have also seen quite a few more complaints about the new ASP.Net than
about other types of projects, such as Windows Forms, Services, and class
libraries. I have yet to do any ASP.Net work with the new Visual Studio, so
I can't say anything about that. But I have written quite a few other
projects, including Windows Forms, Services, and class libraries, without
any performance issues.
In addition, I have observed that VS.Net 2005 is far superior to VS.Net 2003
in many ways, too many to enumerate here, except to mention a few of the
more obvious improvements. Intellisense is much improved. Refactoring is a
real time-saver. Support for standards, in particular those involving XML is
incredible. And DTDs are used for error-checking and intellisense, which
makes a heck of a lot of sense.
I wouldn't go back to VS.Net 2003 for any reason, other than to maintain
legacy (1.1) applications.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.
"Jeff" <A@B.COM> wrote in message
news:Oi******** *****@TK2MSFTNG P12.phx.gbl... Re: << It's not our job to "sway" you >>
Well, yes, of course not. But I'm looking to learn from some of you who have *not* been complaining. Maybe you have not observed the bugs - maybe you just aren't saying anything.
"Gabriel Magana" <no***@nospam.c om> wrote in message news:OA******** ******@TK2MSFTN GP09.phx.gbl... Well, I'm not gonna give you the free lunch you seek (you have to try VS2005 out for yourself), but I can say that the bugs I have run into are worth it for the many benefits that VS2005 brings.
It's not our job to "sway" you... I'm sure there are people still using VS6 because there are too many bugs in subsequent releases, but it is their choice... It's more of a cost/benefit analysis you have to do according to your own values/tolerance/etc...
For example, just yesterday I fixed a long-standing layout bug in one of our aspx pages just because of the collapsible tags in the VS2005 HTML editor. The collapsible tags feature, in conjunction with the new integrated HTML code formatter, allowed me to greatly simplify how the HTML was displayed, making the syntax error very simple to catch. This was an error that I had spent searching for at least a full day with VS2003... But the VS2005 came with some bugs, including some pretty big ones when it comes to deployment of web sites and also a very annoying bug in which VS2005 checks into source control files under the /bin directory when clearly, nothing in that folder should be checked into source control. Is it worth the upgrade? Absolutely, even through there are bugs, the benefits hugely outweight the annoyances for me.
You have to make a similar evaluation and decision, based on your needs.
"Jeff" <A@B.COM> wrote in message news:O4******** ******@TK2MSFTN GP12.phx.gbl... RE: << Have you actually tried it?... >>
No, because I have work to do. And no, I'm not flaming or being negative. I'm a *huge* fan of Microsoft. I also have a lot of time constraints and simply don't have the time to screw around with a product which, given all of the chatter in the varous Microsoft NGs, was apparently rushed to market (or at least not fully developed when released). It appears that one one must be willing to deal with slow performance, random "freezing", machine crashes, etc. Given the volume of reports I think it's reasonable to conclude that I would likely experience similar symptoms.
So while I'm looking to play it safe I also don't want to be obviously and unnecessarily cautious. So I guess I'd be swayed to go with VS 2005 right away if a number of people responded to my post here claiming that they were totaly happy with VS 2005 and that they *never* experience any of the frequently reported "buggy" behaviour.
-Jeff
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c om> wrote in message news:up******** ******@tk2msftn gp13.phx.gbl... Not only that, but you are pretty much going to miss out on a good amount of functionality which VS.NET 2005 provides.
Have you actually tried it? I ask because you say apparent...
-- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard. caspershouse.co m
"Stefan Nuxoll" <ne******@gmail .com> wrote in message news:11******** *****@corp.supe rnews.com... > Jeff wrote: >> Looking for your highly subjective opinions (from those of you who >> have been working extensively with VS 2005). >> >> I have a client that needs/wants a complete rewrite of an existing >> application. I will be proposing a .NET Windows application with a >> supporting SQL Server database. It will likely take 4-5 months before >> we roll out the first production version. >> >> Because of the apparent issues with VS 2005 (poor performance, >> unpredictable and generally buggy behaviour), I am thinking it might >> make sense to develop this app in VS.NET 2003/.NET 1.1. Then, around >> the time we're ready to roll out the first production version, >> migrate it to .NET 2.x just before going live. >> >> I say 2.x because Microsoft has plans to release a service pack for >> it mid-way through 2006, so we might have a minor version number >> change at that time. Also, it appears that the service pack from >> Microsoft, if released mid-year, will stabilize things so we can >> [hopefully] have a smooth transition to 2.x just before going live. >> >> Does this strategy make sense? Thoughts? Opinions? >> >> Thanks! > This makes some sense, however doing something in this fashion is not > recommended as some things may go haywire during the conversion > process that you would need to fix. I find it easier just to deal > with VS 2005 and make it with .NET 2.0 to start.
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Arun Bhalla |
last post by:
I'm working with VS.NET 2003 and .NET 1.1 (not SP1) on Windows XP SP1. My
application is using the Windows Installer Bootstrap. (I may have also
installed a module which detects requirements (.NET 1.1 -> MsiNetAssembly
Support.) I have a few issues and questions regarding the MSI and its
properties.
* This may be my biggest annoyance at the moment. When the installer creates
the target directory, it's setting them as read-only. When the...
|
by: chuliu |
last post by:
I want to develop the project from my home pc and the project is originally in my office developing by a group of developers, myself included. VSS is implemented. I am running win2k pro in my office pc which has visual studio .net installed. The source safe server is on another pc. I tried to zip the source code from my office pc running win2000 and take it home to my home pc running winxp and also has visual studio .net. However, when I...
|
by: George Copeland |
last post by:
This is a request for assistance analyzing a problem we are experiencing in
our VB6 development environment. All our code is developed in VB6, and our
persistance layer is SQL Server. We are planning to convert this project to
dot net sometime in the future.
Our architecture is an exe project with references to four business object
dlls. Also, each one of our tables is encapsulated in a data object dll.
The data objects are referenced...
|
by: Jeff |
last post by:
Looking for your highly subjective opinions (from those of you who have been
working extensively with VS 2005).
I have a client that needs/wants a complete rewrite of an existing
application. I will be proposing a .NET Windows application with a
supporting SQL Server database. It will likely take 4-5 months before we
roll out the first production version.
Because of the apparent issues with VS 2005 (poor performance, unpredictable
and...
|
by: garethdjames |
last post by:
I work for a large organisation where we use .Net 1.1 as our sole
development language.
We have many frameworks and applications and web sites that are
developed in .Net 1.1
These developments are by no means trivial, they are the result of an
IT department of over 300 people and 2 years of development
It is my responsibility to develop a strategy to move to .Net 2.0, this
| |
by: robinsand |
last post by:
My apologies to those of you who are more advanced Visual C++ .NET
programmers, but I am working on a project for an MBA course that is
condensed into an eight-week schedule, and I need help getting a
program up and running with proper files and documentation to be handed
in for a grade (on Microsoft Visual Studio .NET 2003).
I am being graded on how well I incorporate advanced C++ features such
as inheritance, polymorphic programming,...
|
by: Tony Girgenti |
last post by:
Hello.
I'm developing and testing a web application using VS.NET 2003, VB, .NET
Framework 1.1.4322, ASP.NET 1.1.4322 and IIS5.1 on a WIN XP Pro, SP2
computer. I'm using a web form.
How do I move this project/solution from a local development xp pro computer
which uses IIS/localhost, to another xp pro computer that is on a Windows
2003 server domain. I want to be able to use the Windows 2003 server IIS
instead of localhost.
|
by: marcin.rzeznicki |
last post by:
Hello everyone
I've got a little problem with choosing the best decoding strategy for
some nasty problem. I have to deal with very large files wich contain
text encoded with various encodings. Their length makes loading
contents of file into memory in single run inappropriate. I solved this
problem by implementing memory mapping using P/Invoke and I load
contents of file in chunks. Since files' contents are in different
encodings what I...
|
by: gunimpi |
last post by:
http://www.vbforums.com/showthread.php?p=2745431#post2745431
********************************************************
VB6 OR VBA & Webbrowser DOM Tiny $50 Mini Project Programmer help
wanted
********************************************************
For this teeny job, please refer to:
http://feeds.reddit.com/feed/8fu/?o=25
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
| |
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
| |
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |