Vitaliy > Could you tell me the approximative date (month) when you'd plan to release > the source code for visual studio 2010 and recent intel compilers? No, sorry, it will depend on whether we can recruit a new staff member to work on the Windows port and if so, the level of expertise that person has to adapt netCDF to the Windows VS and .Net development environment. If you know of any exceptional developers who would be interested in coming to Boulder to work on netCDF and porting to Windows, please let them know we will be posting a job description in a couple of weeks for a new position at Unidata. > P.S. > I'm trying the latest version for Visual Studio (v4.1.1 and v4.1.3). > - v4.1.1 can read *.nc but cannot write nc files (link problem with > nf_create routine) > - v4.1.3 can be built but has runtime error when initializing netcdf.dll There are also some more recent DLLs available for testing, as announced in this posting to the netcdfgroup mailing list in May: http://www.unidata.ucar.edu/mailing_lists/archives/netcdfgroup/2011/msg00170.html > if it were be possible for the future to create different options for > linking to netcdf under windows (including fortran90 APIs) > - static linking (only lib files) > - dynamic linking (dll and lib files) > -- static /MT release and debug options (with lib files) > -- dynamic /MD release and debug options (with the possiblility of delayed > load) > > the real breakthrougt for netcdf under window would be if there were a C# > (.NET) wrap to call netcdf functions, > in addition, the C# modules (managed dll) that provides XML web-services > and ADO.NET (F# like) communication between netcdf and sql-servers. > perhaps, rewrite netcdf from zero directly in C# would be faster solution... If would be great if we could develop and provide all those Windows-specific solutions. Currently we don't have the resources or Windows-specific skills to do that. Rewriting netCDF in C# would not result in a platform-independent library, so would not be high on our list of priorities. However, getting a reliable Windows port of netCDF is a high priority. Anyway, thanks for the recommendations, if we ever get a C#(.NET) port, we'll try to make it available. --Russ > address@hidden> wrote: > > > Hi Vitaliy, > > > > > I've tried to use old version of static netcdf library (netcdf.lib 856kb) > > > > > > but I have NF_CREATE crash > > > > > > Is there more recent netcdf library for static linking on win32 platform > > ? > > > > The current state of the Windows port is described here: > > > > > > http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#windows_netcdf4_1 > > > > As you can see at the end of that entry, there have been a couple of > > contributions of > > Windows ports from users in the community. (We'll soon be trying to > > recruit and hire a > > Windows developer to provide better Windows support for netCDF, but > > unfortunately that > > won't help much now.) > > > > If you have cygwin, you can build netCDF libraries for Windows from any > > recent release, > > but we don't have any recent solutions for Visual Studio currently. > > > > --Russ > > > > > > Russ Rew UCAR Unidata Program > > address@hidden http://www.unidata.ucar.edu > > > > > > > > Ticket Details > > =================== > > Ticket ID: HSK-896839 > > Department: Support netCDF > > Priority: High > > Status: Closed > > > > > > Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: HSK-896839 Department: Support netCDF Priority: High Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.