reassigned.

mh->obo: as already spoken, we will provide a patch for 1.1 codeline
and will commit changes to 2.0 codeline

set component

This task is identical with #111136#.

There is no #111136#.
Or #11136#, is not same issue.

I hope we can consider which one to use as main development
environtment for Ooo 2.0
- VC++ .net 2004
Not ready for the moments (maybe Feb 2004), didnt know yet the
compatibility or improvements, only this info is available 
http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx
- VC++ .net 2003
Now is available, and have many improvements from 2002. 
- VC++ .net 2002
Not available anymore in the market. Have some compatibility issue
with 2003 or future I guess. 
- VC++ 6
Is very old already. And is not compatible enough with existing VC++
.net or futre version. 
Make new developer has many limitation in using the features available
in new VC++ version

I think better if we use VC++ .net 2004 or VC++ .net 2003 for future
compatibility and flexibility, and make developer can utility the new
features. And especially because it is for long term. 
and it is not only dealing with compiling it, but more to the
development it. 

Best regards,


Utomo

#111136# is an internal ID which I've used to commit changed files
into CVS during .NET 2003 evaluation. 

BTW: I would suggest, not to add comments which you have already
posted on a newsgroup into this task, please.

Oliver.

plan is to use up to date compiler for the living codelines.

we always have to find a compromise:
-if we are close to release we might not take the risk of compiler change
-how long will old compilers be supported. 

Thanks for the info regarding #111136#

I will not post that in here if it is not so important for the future
of OO, and because there is no comment in the mailing list. Sorry . 


Thanks Martin. 
For OOo 2.0 I think we have enough time to change it to VC++ .net 2004
which I belive it is compatible enough with 2003. or at least use 2003
as base codeline. 

.

Hi Jogi, reassigned to you as spoken.

Utomo> Oliver Bolte:
Why it is marked as Fixed ? where is the ConvertDSW ?
and this is for 1.1 codeline, not for 2.0. For 2.0 as Martin
Hollmichel say: it will use the latest tools (maybe VC++ .net 2003 or
2004 which will come in around Feb 2004)

Also the info/ConvertDSW must be available in 
http://tools.openoffice.org/dev_docs/build_windows.html

Thanks

Hi!
Target for this task is OOo 2.0.
ConvertDSW is commited to tools/contrib/addin/bin_net2003.
The patch for OOo 1.1 is created and will be tested by Sander asap. .
This will be announced when its verifiyed.

Created attachment 9868 [details]
Bugdoc with Entities

Grrr. Wrong issue for the attachment, sorry.

Fixed.

verfied

Regarding Visual Studio .net 2004 schedule it is not released in
February 2004, sorry. please read info below. 
http://news.com.com/2100-1016-5057063.html?tag=nl

Hi Sander,
for the OOo 1.1 patch checking (based on SRX645 m18) I've reassigned
this task to you.
Bye,
Oliver.

Hi, 

As this is planned to add patch for 1.1 (as oliver say), do we better
to change the target to OOo 1.1.1 instead of 2.0 ? 
so after Sander verified it, maybe we can build 1.1.1 using .net 2003
(maybe will produce better code than .net 2002)
CMIIW. 
Thanks

Adding myself as CC

Created attachment 11814 [details]
Configure.in patched for .NET 2003

Created attachment 11815 [details]
set_soenv.in patch for .NET 2003

Added patches for config_office for .NET 2003.
Can someone please verify these patches?
Thanks

.NET 2003 depends on #i23309# and #i23204# being resolved

Config patch approved.  Please ensure your autoconf is recent release before
committing configure script.

Comitted to cws_src680_ooo20031216

utomo > dsherwin :
can you explain here how to use that patch. and what important things need to 
do ? 

Thanks

Re-assigning issue to me to close it

Resolving issue to fixed

Closing this issue, .net2003 has been working for while now

Created attachment 72642