473,543 Members | 2,496 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Please Settle This Issue....(URGEN T)

in my head......

I need my application to work with Office 97, 2000, XP and 2003 versions of
MS Word and MS Excel.

IN order to acomplish this I have to install in different folders:

1. remove my Office 2003
2. Install Office 97 Word and Excel
3. Install Office 2000 Word and Excel
4. Install Office XP Word and Excel
5. Reinstall my Office 2003
6. Open my project and add references for Word and Excel libraries 8?-11.
The libraries will be there then right?
7. REbuild project.......

Last time I did something like this I spent weeks trying to fix the mess it
turned into. I tried to install OFfice XP next to 2003 without taking 2003
off.

I so much do not want to go through that again....

Thanks again.

Nov 20 '05 #1
11 1824
You should have Office 97 installed on your development machine, and your
project should only reference the Office 97 type libraries (version 8.0, I
think.)

The application will then be forward compatible to later versions of Office
as well. (In theory at least -- there are reports of a few subtle changes
in the Office object model that can introduce bugs, so test your application
thoroughly with other versions.) You can have other versions of Office
installed on your machine for testing purposes, but it isn't strictly
necessary.
"scorpion53 061" <Its the end of the world as we know it@here.com> wrote in
message news:Of******** ******@TK2MSFTN GP11.phx.gbl...
in my head......

I need my application to work with Office 97, 2000, XP and 2003 versions of MS Word and MS Excel.

IN order to acomplish this I have to install in different folders:

1. remove my Office 2003
2. Install Office 97 Word and Excel
3. Install Office 2000 Word and Excel
4. Install Office XP Word and Excel
5. Reinstall my Office 2003
6. Open my project and add references for Word and Excel libraries 8?-11.
The libraries will be there then right?
7. REbuild project.......

Last time I did something like this I spent weeks trying to fix the mess it turned into. I tried to install OFfice XP next to 2003 without taking 2003
off.

I so much do not want to go through that again....

Thanks again.

Nov 20 '05 #2
Thank you for respoding. Plesae let me know what went wrong here.

After doing this (putting in 8.0) what I had before

Imports Word = Microsoft.Offic e.Interop.Word
Imports Office = Microsoft.Offic e.Core

isnt working. IT is saying:

C:\Documents and Settings\Admini strator\My Documents\Visua l Studio
Projects\MS Word Assistant\fmwor ddoc.vb(2): Namespace or type 'Word' for the
Imports 'Microsoft.Offi ce.Interop.Word ' cannot be found.

C:\Documents and Settings\Admini strator\My Documents\Visua l Studio
Projects\MS Word Assistant\fmwor ddoc.vb(3): Imports alias 'Office' conflicts
with 'Namespace Office' declared in the root namespace.
The dependency 'Interop.VBIDE' could not be found.
"Robert Jacobson" <rj************ **********@nosp am.com> wrote in message
news:OW******** ********@TK2MSF TNGP11.phx.gbl. ..
You should have Office 97 installed on your development machine, and your
project should only reference the Office 97 type libraries (version 8.0, I
think.)

The application will then be forward compatible to later versions of Office as well. (In theory at least -- there are reports of a few subtle changes
in the Office object model that can introduce bugs, so test your application thoroughly with other versions.) You can have other versions of Office
installed on your machine for testing purposes, but it isn't strictly
necessary.
"scorpion53 061" <Its the end of the world as we know it@here.com> wrote in
message news:Of******** ******@TK2MSFTN GP11.phx.gbl...
in my head......

I need my application to work with Office 97, 2000, XP and 2003 versions

of
MS Word and MS Excel.

IN order to acomplish this I have to install in different folders:

1. remove my Office 2003
2. Install Office 97 Word and Excel
3. Install Office 2000 Word and Excel
4. Install Office XP Word and Excel
5. Reinstall my Office 2003
6. Open my project and add references for Word and Excel libraries 8?-11. The libraries will be there then right?
7. REbuild project.......

Last time I did something like this I spent weeks trying to fix the mess

it
turned into. I tried to install OFfice XP next to 2003 without taking 2003 off.

I so much do not want to go through that again....

Thanks again.


Nov 20 '05 #3
Pardon my VB6 here, but using it purly for example.

Isn't the way Microsoft Office products are designed that if you just do a
createobject type issue with

CreateObject("W ord.Application ") it automatically returns the appropriate
version as per the regsitry defintion?

Could we use the same idea here? And only interop the Excel 7.0 (97)
Library to ensure 100% backwards compatiblity?

-CJ

"Robert Jacobson" <rj************ **********@nosp am.com> wrote in message
news:OW******** ********@TK2MSF TNGP11.phx.gbl. ..
You should have Office 97 installed on your development machine, and your
project should only reference the Office 97 type libraries (version 8.0, I
think.)

The application will then be forward compatible to later versions of Office as well. (In theory at least -- there are reports of a few subtle changes
in the Office object model that can introduce bugs, so test your application thoroughly with other versions.) You can have other versions of Office
installed on your machine for testing purposes, but it isn't strictly
necessary.
"scorpion53 061" <Its the end of the world as we know it@here.com> wrote in
message news:Of******** ******@TK2MSFTN GP11.phx.gbl...
in my head......

I need my application to work with Office 97, 2000, XP and 2003 versions

of
MS Word and MS Excel.

IN order to acomplish this I have to install in different folders:

1. remove my Office 2003
2. Install Office 97 Word and Excel
3. Install Office 2000 Word and Excel
4. Install Office XP Word and Excel
5. Reinstall my Office 2003
6. Open my project and add references for Word and Excel libraries 8?-11. The libraries will be there then right?
7. REbuild project.......

Last time I did something like this I spent weeks trying to fix the mess

it
turned into. I tried to install OFfice XP next to 2003 without taking 2003 off.

I so much do not want to go through that again....

Thanks again.


Nov 20 '05 #4
You can do that, but the references to Microsoft Word will then be
late-bound (of type "Object" instead of type "Word.Applicati on.") This is
generally undesirable because you won't be able to use Intellisense in the
IDE, and increases the opportunities for bugs. There might be circumstances
where it's necessary, but it should generally be avoided.
"CJ Taylor" <no****@blowgoa ts.com> wrote in message
news:10******** *****@corp.supe rnews.com...
Pardon my VB6 here, but using it purly for example.

Isn't the way Microsoft Office products are designed that if you just do a
createobject type issue with

CreateObject("W ord.Application ") it automatically returns the appropriate
version as per the regsitry defintion?

Could we use the same idea here? And only interop the Excel 7.0 (97)
Library to ensure 100% backwards compatiblity?

-CJ

"Robert Jacobson" <rj************ **********@nosp am.com> wrote in message
news:OW******** ********@TK2MSF TNGP11.phx.gbl. ..
You should have Office 97 installed on your development machine, and your
project should only reference the Office 97 type libraries (version 8.0, I think.)

The application will then be forward compatible to later versions of

Office
as well. (In theory at least -- there are reports of a few subtle changes in the Office object model that can introduce bugs, so test your

application
thoroughly with other versions.) You can have other versions of Office
installed on your machine for testing purposes, but it isn't strictly
necessary.
"scorpion53 061" <Its the end of the world as we know it@here.com> wrote in message news:Of******** ******@TK2MSFTN GP11.phx.gbl...
in my head......

I need my application to work with Office 97, 2000, XP and 2003
versions of
MS Word and MS Excel.

IN order to acomplish this I have to install in different folders:

1. remove my Office 2003
2. Install Office 97 Word and Excel
3. Install Office 2000 Word and Excel
4. Install Office XP Word and Excel
5. Reinstall my Office 2003
6. Open my project and add references for Word and Excel libraries 8?-11. The libraries will be there then right?
7. REbuild project.......

Last time I did something like this I spent weeks trying to fix the
mess it
turned into. I tried to install OFfice XP next to 2003 without taking

2003 off.

I so much do not want to go through that again....

Thanks again.



Nov 20 '05 #5
I think your're just referencing the wrong library. To control Word, you
should just reference the "Word" namespace, instead of
"Microsoft.Offi ce.Interop.Word ." (This can happen when you switch back and
forth between libraries -- you get more DLLs in the "References " list than
you need, and it becomes a mess.)

It might be easier if you create a new project for testing purposes. This
worked for me (using the Office 2000 libraries -- don't have Office 97
installed on my dev machine):

1. Create a new WinForms application, and drop a button on it.

2. Add a COM reference to the appropriate Word library (8.0 for you.) In
addition to the standard references, you should have "Office," "VBIDE" and
"Word."

3. Insert the following code to handle the button's click event:

Private Sub Button1_Click(B yVal sender As System.Object, ByVal e As
System.EventArg s) Handles Button1.Click

Debug.WriteLine ("Opening Microsoft Word")
Dim App As New Word.Applicatio n

Debug.WriteLine ("Showing Microsoft Word")
App.Visible = True

Debug.WriteLine ("Quitting Microsoft Word")
App.Quit()

End Sub

It will open Word, make it visible, and then close it. It should also work
for any version of Word, 97 and higher.

If this works, then try clearing out all of the extraneous references in
your working application, and then add the reference to the Word 8.0 and/or
Excel 8.0 libraries again. You can just delete the "Imports... " lines and
make sure that your code is referencing the correct libraries.

Hope this helps!
"scorpion53 061" <Its the end of the world as we know it@here.com> wrote in
message news:ut******** *****@TK2MSFTNG P12.phx.gbl...
Thank you for respoding. Plesae let me know what went wrong here.

After doing this (putting in 8.0) what I had before

Imports Word = Microsoft.Offic e.Interop.Word
Imports Office = Microsoft.Offic e.Core

isnt working. IT is saying:

C:\Documents and Settings\Admini strator\My Documents\Visua l Studio
Projects\MS Word Assistant\fmwor ddoc.vb(2): Namespace or type 'Word' for the Imports 'Microsoft.Offi ce.Interop.Word ' cannot be found.

C:\Documents and Settings\Admini strator\My Documents\Visua l Studio
Projects\MS Word Assistant\fmwor ddoc.vb(3): Imports alias 'Office' conflicts with 'Namespace Office' declared in the root namespace.
The dependency 'Interop.VBIDE' could not be found.
"Robert Jacobson" <rj************ **********@nosp am.com> wrote in message
news:OW******** ********@TK2MSF TNGP11.phx.gbl. ..
You should have Office 97 installed on your development machine, and your
project should only reference the Office 97 type libraries (version 8.0, I think.)

The application will then be forward compatible to later versions of

Office
as well. (In theory at least -- there are reports of a few subtle changes in the Office object model that can introduce bugs, so test your

application
thoroughly with other versions.) You can have other versions of Office
installed on your machine for testing purposes, but it isn't strictly
necessary.
"scorpion53 061" <Its the end of the world as we know it@here.com> wrote in message news:Of******** ******@TK2MSFTN GP11.phx.gbl...
in my head......

I need my application to work with Office 97, 2000, XP and 2003
versions of
MS Word and MS Excel.

IN order to acomplish this I have to install in different folders:

1. remove my Office 2003
2. Install Office 97 Word and Excel
3. Install Office 2000 Word and Excel
4. Install Office XP Word and Excel
5. Reinstall my Office 2003
6. Open my project and add references for Word and Excel libraries 8?-11. The libraries will be there then right?
7. REbuild project.......

Last time I did something like this I spent weeks trying to fix the
mess it
turned into. I tried to install OFfice XP next to 2003 without taking

2003 off.

I so much do not want to go through that again....

Thanks again.



Nov 20 '05 #6
What about Word.IApplicati on interface... Shouldn't that have the general
stuff in it for those versions? After all, wasn't that the mindset of
microsoft when they devleoped the office product line, to provide backward
compatitiblity? And isn't that one of the reasons we use interfaces?
"Robert Jacobson" <rj************ **********@nosp am.com> wrote in message
news:ON******** ******@TK2MSFTN GP11.phx.gbl...
You can do that, but the references to Microsoft Word will then be
late-bound (of type "Object" instead of type "Word.Applicati on.") This is
generally undesirable because you won't be able to use Intellisense in the
IDE, and increases the opportunities for bugs. There might be circumstances where it's necessary, but it should generally be avoided.
"CJ Taylor" <no****@blowgoa ts.com> wrote in message
news:10******** *****@corp.supe rnews.com...
Pardon my VB6 here, but using it purly for example.

Isn't the way Microsoft Office products are designed that if you just do a
createobject type issue with

CreateObject("W ord.Application ") it automatically returns the appropriate version as per the regsitry defintion?

Could we use the same idea here? And only interop the Excel 7.0 (97)
Library to ensure 100% backwards compatiblity?

-CJ

"Robert Jacobson" <rj************ **********@nosp am.com> wrote in message
news:OW******** ********@TK2MSF TNGP11.phx.gbl. ..
You should have Office 97 installed on your development machine, and your project should only reference the Office 97 type libraries (version 8.0,
I
think.)

The application will then be forward compatible to later versions of Office
as well. (In theory at least -- there are reports of a few subtle changes in the Office object model that can introduce bugs, so test your

application
thoroughly with other versions.) You can have other versions of
Office installed on your machine for testing purposes, but it isn't strictly
necessary.
"scorpion53 061" <Its the end of the world as we know it@here.com>

wrote in message news:Of******** ******@TK2MSFTN GP11.phx.gbl...
> in my head......
>
> I need my application to work with Office 97, 2000, XP and 2003 versions of
> MS Word and MS Excel.
>
> IN order to acomplish this I have to install in different folders:
>
> 1. remove my Office 2003
> 2. Install Office 97 Word and Excel
> 3. Install Office 2000 Word and Excel
> 4. Install Office XP Word and Excel
> 5. Reinstall my Office 2003
> 6. Open my project and add references for Word and Excel libraries

8?-11.
> The libraries will be there then right?
> 7. REbuild project.......
>
> Last time I did something like this I spent weeks trying to fix the mess it
> turned into. I tried to install OFfice XP next to 2003 without

taking 2003
> off.
>
> I so much do not want to go through that again....
>
> Thanks again.
>
>
>



Nov 20 '05 #7
Do you mean the "Word.Applicati on" interface? You'll only get that if your
project references a type library that defines the interface. Each version
of Word is backwards compatible to applications developed against earlier
versions of Word . (That's because later versions of the Word type library
are binary compatible with earlier versions of the libraries.)
Consequently, if your application references, e.g., the Word 8.0 type
library (Word 97), it will also work with Word 2000 (the Word 9.0 library),
Word XP (the Word 10.0 library), etc.

However, you won't get a strongly-typed interface if you just use
CreateObject, unless you cast the resulting reference from CreateObject to
type "Word.Applicati on." In general, "Dim x as Object =
CreateObject("W ord.Application ")" is evil, while "Dim x as New
Word.Applicatio n" is good.
"CJ Taylor" <no****@blowgoa ts.com> wrote in message
news:10******** *****@corp.supe rnews.com...
What about Word.IApplicati on interface... Shouldn't that have the general
stuff in it for those versions? After all, wasn't that the mindset of
microsoft when they devleoped the office product line, to provide backward
compatitiblity? And isn't that one of the reasons we use interfaces?
"Robert Jacobson" <rj************ **********@nosp am.com> wrote in message
news:ON******** ******@TK2MSFTN GP11.phx.gbl...
You can do that, but the references to Microsoft Word will then be
late-bound (of type "Object" instead of type "Word.Applicati on.") This is
generally undesirable because you won't be able to use Intellisense in the IDE, and increases the opportunities for bugs. There might be circumstances
where it's necessary, but it should generally be avoided.
"CJ Taylor" <no****@blowgoa ts.com> wrote in message
news:10******** *****@corp.supe rnews.com...
Pardon my VB6 here, but using it purly for example.

Isn't the way Microsoft Office products are designed that if you just do a createobject type issue with

CreateObject("W ord.Application ") it automatically returns the appropriate version as per the regsitry defintion?

Could we use the same idea here? And only interop the Excel 7.0 (97)
Library to ensure 100% backwards compatiblity?

-CJ

"Robert Jacobson" <rj************ **********@nosp am.com> wrote in
message news:OW******** ********@TK2MSF TNGP11.phx.gbl. ..
> You should have Office 97 installed on your development machine, and

your
> project should only reference the Office 97 type libraries (version 8.0,
I
> think.)
>
> The application will then be forward compatible to later versions of
Office
> as well. (In theory at least -- there are reports of a few subtle

changes
> in the Office object model that can introduce bugs, so test your
application
> thoroughly with other versions.) You can have other versions of

Office > installed on your machine for testing purposes, but it isn't strictly > necessary.
>
>
> "scorpion53 061" <Its the end of the world as we know it@here.com> wrote
in
> message news:Of******** ******@TK2MSFTN GP11.phx.gbl...
> > in my head......
> >
> > I need my application to work with Office 97, 2000, XP and 2003

versions
> of
> > MS Word and MS Excel.
> >
> > IN order to acomplish this I have to install in different folders:
> >
> > 1. remove my Office 2003
> > 2. Install Office 97 Word and Excel
> > 3. Install Office 2000 Word and Excel
> > 4. Install Office XP Word and Excel
> > 5. Reinstall my Office 2003
> > 6. Open my project and add references for Word and Excel libraries
8?-11.
> > The libraries will be there then right?
> > 7. REbuild project.......
> >
> > Last time I did something like this I spent weeks trying to fix

the mess
> it
> > turned into. I tried to install OFfice XP next to 2003 without

taking 2003
> > off.
> >
> > I so much do not want to go through that again....
> >
> > Thanks again.
> >
> >
> >
>
>



Nov 20 '05 #8

"Robert Jacobson" <rj************ **********@nosp am.com> wrote in message
news:O%******** *******@tk2msft ngp13.phx.gbl.. .
Do you mean the "Word.Applicati on" interface? You'll only get that if your project references a type library that defines the interface. Each version of Word is backwards compatible to applications developed against earlier
versions of Word . (That's because later versions of the Word type library are binary compatible with earlier versions of the libraries.)
Consequently, if your application references, e.g., the Word 8.0 type
library (Word 97), it will also work with Word 2000 (the Word 9.0 library), Word XP (the Word 10.0 library), etc.

However, you won't get a strongly-typed interface if you just use
CreateObject, unless you cast the resulting reference from CreateObject to
type "Word.Applicati on." In general, "Dim x as Object =
CreateObject("W ord.Application ")" is evil, while "Dim x as New
Word.Applicatio n" is good.
I understand the difference between strong typing and weak typing or
latebinding vs. earlybinding, whatever you want to call it. But I'm trying
to help you solve your problem given you know nothing of what your user has
installed.

So, you want to use strongly typed so you can use intellisense, well fair
enough. Then reference your oldest library you have, which should guaruntee
your backwards compatibilty, but don't Dim X as new Word.Applicatio n,
because you create a constraint at that point.

Instead type it and use CreateObject. You still have your intellisense,
maybe not for all the features in XP, but then again, you could check to see
what versions of office are availible on the host machine.

I hope you understand I'm tyring to just give you a really simple solution
to the problem without having to do all sorts of version checks/go through
the mess you were going to go through earlier.

Good luck,
CJ


"CJ Taylor" <no****@blowgoa ts.com> wrote in message
news:10******** *****@corp.supe rnews.com...
What about Word.IApplicati on interface... Shouldn't that have the general
stuff in it for those versions? After all, wasn't that the mindset of
microsoft when they devleoped the office product line, to provide backward compatitiblity? And isn't that one of the reasons we use interfaces?
"Robert Jacobson" <rj************ **********@nosp am.com> wrote in message
news:ON******** ******@TK2MSFTN GP11.phx.gbl...
You can do that, but the references to Microsoft Word will then be
late-bound (of type "Object" instead of type "Word.Applicati on.") This
is generally undesirable because you won't be able to use Intellisense in the IDE, and increases the opportunities for bugs. There might be circumstances
where it's necessary, but it should generally be avoided.
"CJ Taylor" <no****@blowgoa ts.com> wrote in message
news:10******** *****@corp.supe rnews.com...
> Pardon my VB6 here, but using it purly for example.
>
> Isn't the way Microsoft Office products are designed that if you
just do
a
> createobject type issue with
>
> CreateObject("W ord.Application ") it automatically returns the

appropriate
> version as per the regsitry defintion?
>
> Could we use the same idea here? And only interop the Excel 7.0
(97) > Library to ensure 100% backwards compatiblity?
>
> -CJ
>
> "Robert Jacobson" <rj************ **********@nosp am.com> wrote in

message > news:OW******** ********@TK2MSF TNGP11.phx.gbl. ..
> > You should have Office 97 installed on your development machine, and your
> > project should only reference the Office 97 type libraries (version 8.0,
I
> > think.)
> >
> > The application will then be forward compatible to later versions
of > Office
> > as well. (In theory at least -- there are reports of a few subtle
changes
> > in the Office object model that can introduce bugs, so test your
> application
> > thoroughly with other versions.) You can have other versions of

Office
> > installed on your machine for testing purposes, but it isn't

strictly > > necessary.
> >
> >
> > "scorpion53 061" <Its the end of the world as we know it@here.com>

wrote
in
> > message news:Of******** ******@TK2MSFTN GP11.phx.gbl...
> > > in my head......
> > >
> > > I need my application to work with Office 97, 2000, XP and 2003
versions
> > of
> > > MS Word and MS Excel.
> > >
> > > IN order to acomplish this I have to install in different folders: > > >
> > > 1. remove my Office 2003
> > > 2. Install Office 97 Word and Excel
> > > 3. Install Office 2000 Word and Excel
> > > 4. Install Office XP Word and Excel
> > > 5. Reinstall my Office 2003
> > > 6. Open my project and add references for Word and Excel libraries > 8?-11.
> > > The libraries will be there then right?
> > > 7. REbuild project.......
> > >
> > > Last time I did something like this I spent weeks trying to fix the mess
> > it
> > > turned into. I tried to install OFfice XP next to 2003 without

taking
> 2003
> > > off.
> > >
> > > I so much do not want to go through that again....
> > >
> > > Thanks again.
> > >
> > >
> > >
> >
> >
>
>



Nov 20 '05 #9
You don't need to use version checks on the host machine -- it doesn't
matter which version of Office the client has installed. If I develop an
application using the Word 97 type libraries on my development machine, it
will automatically work on a client machine that uses Word 2000, Word XP or
Word 2003.

It's a very simple solution -- things just got messy here because Scorpion
was trying to reference different versions of the type library, which was
unnecessary.
[Snip]
So, you want to use strongly typed so you can use intellisense, well fair
enough. Then reference your oldest library you have, which should guaruntee your backwards compatibilty, but don't Dim X as new Word.Applicatio n,
because you create a constraint at that point.

Instead type it and use CreateObject. You still have your intellisense,
maybe not for all the features in XP, but then again, you could check to see what versions of office are availible on the host machine.

I hope you understand I'm tyring to just give you a really simple solution to the problem without having to do all sorts of version checks/go through
the mess you were going to go through earlier.

Good luck,
CJ

Nov 20 '05 #10

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
1191
by: semassaq4 | last post by:
DEAR FRIEND, THROUGH THE COURTESY OF BUSINESS OPPORTUNITY, I TAKE LIBERTY ANCHORED ON A STRONG DESIRE TO SOLICIT YOUR ASSISTANCE ON THIS MUTUALLY BENEFICIAL AND RISKFREE TRANSACTION WHICH I HOPE YOU WILL GIVE YOUR URGENT ATTENTION. I AM MR.SESAY MASSAQUOE I AM MOVED TO WRITE YOU THIS LETTER ,THIS WAS IN CONFIDENCE CONSIDERING OUR PRESENT...
8
1964
by: daniel.w.gelder | last post by:
Hello, I have been trying to write a functor template for a week now and I'm just having tons of trouble because I don't understand an issue that I guess is pretty basic to this task. functor<bool (long, long)> myFunctor; myFunctor = AFunctionOfThatPrototype; To get that much is elementary because the template can just store a...
4
1914
by: ELEMA.LO | last post by:
Hi all, I installed several times the xml analysis provider but I am having severe issues in having it working on a Windows 2003 server machine. I followed all the described steps including adding and enabling a Web service extension for that dll. Also read and execute permissions are setted up; all seems exactly the same to what I did other...
3
8026
by: JenHu | last post by:
Hi experts, In my asp.net application, I use VB.NET code. I want to have a yes/no button in my popup message box when user click "Submit" button. It will check if the employee is a rehire, if yes, delete record from tableA, if no, add record to table B. I understand it might require to have a javascript for this popup box, but :cry: I...
17
2267
by: Saps | last post by:
Hi all. Can anyone help me here. I have loads of .sql files and i need a way to call these from my asp page so the user can run them from the browser. Meaning i have a page with a list of all scripts. each when clicked i am able to run the script. so HOW and what do i do to call and run the .sql Thanks
5
1548
by: uanmi | last post by:
There is a patch to upgrade UAB2 to dotnet 2 on gotdotnet But, as normal, there are no instructions on what to do to patch the Microsoft UAB 2 install. Can Microsoft please upgrade their UAB2 installer to support dotnet 2 now. I really need help urgently as I am completely lost due to the changes that I'm expected to use a crystal ball...
8
2676
by: John Austin | last post by:
I need to understand why if I add a control and use AddHandler to connect its click event, it will work in Page_Load, but not in a Button_Click. The idea is that the user types some data, presses the button, gets a list of results (each with a LinkButton) and can then press one of the link buttons to get further information. The newly added...
14
5656
by: mlw | last post by:
Do not take anything about this, it is not a flame or troll, while I'm not new to Java I favor C++. However, I may need to use it in a contract position, and am concerned that the restrictions it places on application code. Take, for instance, this C++ construct: class foo { char *m_name;
6
5462
by: xhe | last post by:
I am using ffmpeg to convert video, this is a sample script: $str='/home/transla1/bin/ffmpeg -i /home/transla1/public_html/ cybertube/web/uploads/video/31_AK000005.AVI -s 240x180 -b 100k -ar 22050 -y /home/transla1/public_html/cybertube/web/uploads/video/ generated/31_70_AK000005.AVI.flv '; //exec($str); runExternal($str,$code); echo...
0
7408
marktang
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...
0
7349
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language...
0
7590
Oralloy
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. ...
1
7347
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For...
0
5885
agi2029
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...
1
5271
isladogs
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...
0
4895
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...
0
3391
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
968
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.