jkodroff
September 14th, 2005, 11:30 AM
I can't compile my application all of the sudden, and I don't know why.
I have a project with the following structure:
Solution
ASP.NET Project
Business Objects Project
Both my projects reference a libarary called NullableTypes.dll, and it exists in each of their respective bin/ folders. In Visual Studio, the references appear to be ok (no yellow caution/warning icons), yet when I try to compile the application I get something like:
[path stuff here]grantapp2.aspx.vb(159): 'Public Overridable NotOverridable ReadOnly Property IsNull() As Boolean' is declared in project 'NullableTypes.dll', which is not referenced by project 'MegoExternal.dll'.
This happens on every line where I try to use a NullableTypes function/data type, but only in the ASP.NET project - the business objects project compiles fine.
More importantly, my lead developer has the same latest version that I do and can compile the application just fine.
I have verfied that the file is where it should be.
My best guess is that this is a file permissions issue or a SourceSafe issue (i.e VSS corrupting my .vbproj file?), but I need help ASAP. Suggestions GREATLY appreciated.
JK
I have a project with the following structure:
Solution
ASP.NET Project
Business Objects Project
Both my projects reference a libarary called NullableTypes.dll, and it exists in each of their respective bin/ folders. In Visual Studio, the references appear to be ok (no yellow caution/warning icons), yet when I try to compile the application I get something like:
[path stuff here]grantapp2.aspx.vb(159): 'Public Overridable NotOverridable ReadOnly Property IsNull() As Boolean' is declared in project 'NullableTypes.dll', which is not referenced by project 'MegoExternal.dll'.
This happens on every line where I try to use a NullableTypes function/data type, but only in the ASP.NET project - the business objects project compiles fine.
More importantly, my lead developer has the same latest version that I do and can compile the application just fine.
I have verfied that the file is where it should be.
My best guess is that this is a file permissions issue or a SourceSafe issue (i.e VSS corrupting my .vbproj file?), but I need help ASAP. Suggestions GREATLY appreciated.
JK