Re: VB.Net not building added file


"Chris Dunaway" <dunawayc@xxxxxxxxx> wrote in message
news:1181223201.594642.60740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 6, 1:34 pm, "tshad" <t...@xxxxxxxx> wrote:
My mistake.

The file is being built. I looked at the bin folder and found
DbObject.dll
there.

What was happening was that I still had to manually add a reference to
it.
I would have thought that if the project was building the .dll, it would
automatically know about the reference. Apparently I was wrong there.

Definately not intuitive.

Tom

"tshad" <t...@xxxxxxxx> wrote in message

news:%23OQqEfGqHHA.2652@xxxxxxxxxxxxxxxxxxxxxxx

I am using VB.Net 2003 and have added an existing file to my project but
can't seem to get the file to compile and my other file is getting
errors
when refering to it.

The file starts out:
*******************************************************
Imports System
Imports System.Data
Imports System.Data.SqlClient

Namespace MyFunctions

' DbObject is the class from which all classes in the Data Services
Tier
' inherit. The core functionality of establishing a connection with
the
' database and executing simple stored procedures is also provided by
' this base class.
' ---
Public Class DbObject
********************************************************

The file has "MyFunctions" as its' namespace and DbObject as the class.

But in my main file I have the following:

**********************************************************
Imports System.Threading
Imports System.Data
Imports System.Data.SqlClient
Imports System.IO
Imports FtsData
Imports MyFunctions

Module Module1
Dim SqlConnection1 As SqlConnection
Public debugging As Boolean = True
Dim strProgress As String
Dim mutexFile As Mutex
Dim strErrors As String
Dim newPosition As Position
Dim myDbObject As New DbObject
******************************************************

I get the errors:

Namespace or type 'MyFunctions' for the Imports 'MyFunctions' cannot be
found.
Type 'DbObject' is not defined.

Why is this? Why won't it build the added file?

Thanks,

Tom

If you have the source code for the .dll, dont reference the .dll
directly, instead reference the project. That is the preferred
method.

How do you reference the probject?

When you add a reference - you need to point at a .dll? I don't believe you
can reference the project.

Thanks,

Tom
Chris



.

Relevant Pages

  • RE: File Picker Dialog
    ... Must be in the .dll file that I have the problem. ... I can exactly replicate your error by removing the reference to the MS ... Dim strFileName As String ... Microsoft Active X Data Objects 2.1 Library ...
    (microsoft.public.access.modulesdaovba)
  • Re: Late Binding Problem between Excel and Project
    ... That is the reference that you need. ... Earlier you said yours required a VB6 dll, what might that be and why not ... Dim sPath As String ... "Dave Peterson" wrote: ...
    (microsoft.public.excel.programming)
  • Re: VB.Net not building added file
    ... What was happening was that I still had to manually add a reference to it. ... Imports System.Data.SqlClient ... Dim SqlConnection1 As SqlConnection ... Dim myDbObject As New DbObject ...
    (microsoft.public.dotnet.languages.vb)
  • Re: ActiveSync
    ... If you've got the DLL, simply adding a reference and an "Imports" statement ... >>> the Pocket PC and the Desktop WITHOUT the user having to get into the ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: how to reference feild data -
    ... > Imports System.Data ... > Dim conn As New ADODB.Connection ... reference the proper field by specifing the name or the index. ...
    (microsoft.public.data.ado)