Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / C# / October 2007

Tip: Looking for answers? Try searching our database.

getting errors while compiling the program written in .NET framework 1.1 using Visual c# 2005 Express Edition

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Manikandan - 22 Oct 2007 22:41 GMT
Hi,
I have a program written in .Net Framework 1.1 using Visual studio
enterprise edition 2003.
I tried compiling the same program in visual c# express edition 2005.

I'm getting following errors
1.Error 6 Cannot implicitly convert type 'mscomctl.Toolbar []' to

'mscomctl.Toolbar . An explicit conversion exists (are you missing a

cast?)

2.Error 8 Cannot implicitly convert type 'ADODB.Connection []' to

'ADODB.Connection . An explicit conversion exists (are you missing a

cast?)

3.Error 7 The type 'ADODB.Connection' is defined in an assembly that
is

not referenced. You must add a reference to assembly 'ADODB,

Version=2.5.0.0, Culture=neutral, PublicKeyToken=5f3923b67859be87'.

4.Error 10 Cannot implicitly convert type 'ADODB.Recordset []' to

'ADODB.Recordset An explicit conversion exists (are you missing a

cast?)

5.Error 12 Argument '2': cannot convert from 'ADODB.Recordset

6.Error 15 Argument '2': cannot convert from 'ADODB.ExecuteOptionEnum

to 'ADODB.ExecuteOptionEnum []'
7.
Error 21 Assembly generation failed -- Referenced assembly

'Interop.ADODB' does not have a strong name ExcelInterop

I have referenced all assemblies.
The dll referenced are
1.ADOR
2.Interop.ADODB
3.MSCOMCTL.interop
4.stdole
5.Excel interop

I tried to solve the above the errors, but not possible

Is it possible to compile an application written in .NET 1.1
Framework
using visual c# express edition 2005.I'm mainly using excel(web
office
components in my program) for the application
Kindly help me out to solve the errors

Thanks,
Mani
Nicholas Paldino [.NET/C# MVP] - 23 Oct 2007 21:48 GMT
Manikandan,

   I don't think that this is a framework issue.  I think that if you
regenerate your interop assemblies, it should work.

Signature

         - Nicholas Paldino [.NET/C# MVP]
         - mvp@spam.guard.caspershouse.com

> Hi,
> I have a program written in .Net Framework 1.1 using Visual studio
[quoted text clipped - 56 lines]
> Thanks,
> Mani
Manikandan - 28 Oct 2007 10:06 GMT
Hi,
Thanks for your valuable reply.
You are right.
I tried regenerating the interop assembly , but not succeed.
I have a question reg excel interop.
I have no excel installation(office installation) in my system
I'm using office web components in my application.
I tried using tlbimp, getting error as below

TlbImp : error TI0000 : The input file 'C:\DEV\test\ExcelInterop\O
WC11.dll' is not a valid type library.

tried with Interop.OWC11.dll also, getting same error.

TlbImp : error TI0000 : The input file 'C:\DEV\test\ExcelInterop
\Interop.OWC11.dll' is not a valid type library.

I don't know how to regenerate excel interop assembly. is  there any
help available to use office web components in c# windows application?

Thanks,
Mani

> Manikandan,
>
[quoted text clipped - 65 lines]
> > Thanks,
> > Mani

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.