Settings' Is Ambiguous Between Declarations In Modules?
Nov 7, 2011
I'm new to programming. I'm using Visual Studio 2010. I'm taking into two introduction classes, VB and C# with .Net. I have seen the enemy and he is me. I hope that someone can please help me with my two errors.
I do not know how I created My.CopyOfMySettingsProperty but I do know they were created when I was trying to create a project by combining my previous four projects.Listed are the two errors from my error list window that I need to correct along with my offending code:
Error 1 'Settings' is ambiguous between declarations in Modules 'Assign5Multi.My.MySettingsProperty' and 'Assign5Multi.My.CopyOfMySettingsProperty'. F:ProjectsVBAVBAssignment4MoviesMy ProjectSettings.Designer.vb 34 13 prjAssign5Multi
I am getting the error: 'User' is ambiguous between declarations in Modules 'My.MyProject' and 'My.MyProject'.I am trying to debug an ASP.NET web application compiled as a file system project. Obviously the namespaces in question are in-built Microsoft namespaces so there is no way to change anything here nor change any class definitions.
"Error 1 'Application' is ambiguous between declarations in Modules 'WindowsApplication1.My.MyProject' and 'WindowsApplication1.My.MyWpfExtension'.F:DevVisualBasic 2010ProjectsWindowsApplication1WindowsApplication1My ProjectSettings.Designer.vb 33 16 WindowsApplication1"
Yesterday I opened Visual Studio (2008 v 9.0.30729.1) and all the winform classes in my project display with class module icons with the little 'VB', instead of form module icons with the little form icon!
When I double click on a form module, the form designer doesn't open, just the code module.
When I run the project, it runs fine. There are no errors. The project builds fine.
I did Project --> show all files, and I can see the designer and resx files below the form module which doesn't look or act like a form module.
Type Record A As Long B As String End Type Dim Rec As Record
When I keyed in "Type" in my declarations, I was asked to change it to "Structure". After that, I was not able to define anything inside. So, what do I need to do?
I'm trying to learn more about assembly security (something I have basically neglected until recently because security in general is such a huge topic), and I have a question about CAS assembly level declarations.I get how to use them (basically) and the more blunt points of the subect, but I'm still not clear on where assembly level declarations should be made. Basically, where in the solution do you put:
Private Declare Function ReadProcessMemory Lib "kernel32" Alias "ReadProcessMemory" (ByVal hProcess As Integer, ByVal lpBaseAddress As Integer, ByRef lpBuffer As Integer, ByVal nSize As Integer, ByRef lpNumberOfBytesWritten As Integer) As Integer
[Code]...
This correctly returns the memory value as string. So yeah, now it's just the Single that's causing issues.
It is my understanding that all modules are initialized and that all their variables are set up prior to MyApplication_Startup. I have code that has worked well for quite some time (XP and Vista).The Myapplication_Startup code references variables and code located in a Module.However, with Windows 7 this does not work.Anny reference to a module (Data, SUB or FUNCTION) throws a Type Initialization error at runtime. How can I correct this behavior in Windows 7?
I Changed the following: Dim UserFile As New System.IO.StreamReader(sPath & "" & UsernameBox.Text & ".txt")Dim aString As String = UserFile.ReadToEnd() (The code above says that 'UserFile' and 'aString' are Unused variables)
Although I have been programming for many years, successfully, in many different languages, translating my large Word VBA application into VB 2008 Express is driving me crazy. While I understand the theory of OOP and have even been on object-oriented courses, it seems I can't declare my objects correctly and use them in my code. As far as I know, I'm not trying to do more than the "language" is capable of doing, but here goes.
I want to start with "aList" which would be a Collections.Generic.Dictionary(Of String, String) object. Then I want a "bList" which is also a a Collections.Generic.Dictionary object. I would like each bList item to have a few individual simple properties (like a Byte and a String) then an aList instance as well. The application then gets a bList key value from the user, "copies" the corresponding bList item values into a work area, and does the necessary processing using the various bList(aList) / aList(bList) item values from the work area. I say "copies" because I assume that part is simply going to be a pointer copy rather than a long copy of lots of strings. Note that I really don't want to start using arrays here, as the application makes alot of use of Word VBA Dictionaries and I'd like to keep it that way if I can. Incidentally, so far, I have all my global data declarations in a separate Class, not on any of the application's forms.
I want the module to execute first before anything else, and so I call module.main() from the MyApplication startup event. At about the point that program execution gets to the beginning of module-level declarations in the module, it also starts running though the class-level declarations in the thread classes, but long before the threads are declared or the threads are started in the module code. I can't figure out why it happens! Is there some way of supressing that until later (i.e when those classes are actually instantiated)?
On my main application i have a button which shows an "advanced options" form, if the "debug" is checked i was trying to enable/disable visability of a couple of text boxes on the applications main screen but when i tried:
What's the difference between these two declarations for PInvoking a user32.dll function?The first way, which I've commented out since it gets an error (Type DllImport is not defined"), the second way works. [code]
I have an issue with variables that are used to name For-Next loops. I have had this problem in a couple programs but not consistently, i.e. some variables work, some throw a warning (not an error).
The situation is this. I declare the variable along with all my declarations in a module-
Module MainModule Public Counter1 As Integer end Module 'MainModule
[Code]....
The type for variable 'Counter1' will not be inferred because it is bound to a field in an enclosing scope. Either change the name of 'Counter1', or use the fully qualified name (for example, 'Me.Counter1' or 'MyBase.Counter1'). In the past I've always broken down and changed the names to get rid of all those ugly warnings. Sometimes I have eliminated them from being declared in the module and declared them at call time. This is not how I program and I like to keep consistency throughout.
how I can get rid of this spotty, on-and-off nonsense? There is obviously a lot I don't understand about VS and I would have never taken it up but would have stopped 3 languages ago if I weren't forced into bulkier and bulkier languages (sorry about the rant. I feel OK now).
Dim wBrowser As New WebBrowserTabControl1.SelectedTab.Controls.Add(wBrowser)I used the above code to add a WebBrowser to a tab, but I have no idea how to use declarations for it after adding it in code. I'm mainly after the
I've read several articles and questions/answers that conclude the best practice is to let the JIT compiler do all the optimization for inline function calls. Makes sense. What about inline variable declarations? Does the compiler optimize these as well?
[Code]...
Of course I prefer the latter because it's easier to read and debug, but I can't afford the performance degradation if it exists. I have already identified this code as a bottleneck -- No need for retorts about premature optimization.
In my code the application will restart using the Application.Restart statement from another form named frmDatabase.
The application seems to restart while debugging but yet the dataset, tables etc which is declared right below the class declaration for the startup form seems to fail initializing when the restart is done.
Compiling and running the application works like a charm and there is no error like this when running the executeable.
I also Inserted a breakpoint in the Form_Load event and the debugger seems to skip all the statements when the application is restarted all the way down to where the exception occurs.
Declarations:
Public Class frmMain Public objConnection As New OleDbConnection(strConnectionString) Public objDataSet As New DataSet Public objCommand As New OleDbCommand Public objDataAdapter As New OleDbDataAdapter(objCommand)
I am having trouble doing something that is probably pretty simple!I have a stock listing that is done by 1) a simple form with parameters (Index) and 2) an ajax called partial view that displays the list of stock (based on the params).On this same simple form (Index) I have an action link to an "Add Stock" method which calls another form for adding stock.When the user has finished adding the stock I redirect them back to the stock list page (Index).
My issue is that I would like to "remember" the parameters that were initially entered in this form so the user isn't just directed back to a page with blank parameters forcing them to enter them again.I thought I could simply overload the Index method as such:
[Code]...
I get this error: The current request for action 'Index' on controller type 'StockController' is ambiguous between the following action methods:.Now I have read this post and it's answer but I cannot figure out how to implement the solution. Is this solution applicable in my situation? Is there a better way to acheive what I'm trying to do?
I use asp.net user management in my Website.(ASP.NET 3.5) Everything has been working fine while developing and test via VS2010 on Win7. But when I compile and publish the site throws the error:
Compiler Error Message: BC30554: 'ProfileCommon' is ambiguous. Line 55: End Sub Line 56: Line 57: Protected ReadOnly Property Profile() As ProfileCommon
We have a VB web application that for some reason breaks when some clients run Windows Updates. To resolve the issue we have to force the application to recompile on the servers where the application is installed. In some instances we must do this multiple times and/or restart IIS as well to resolve the issue.
This didn't start happening until October of 2009, and then suddenly it happened all the time... but not for every client, and not with every update. It continues to happen and we have been at a loss to understand why. Is anyone else experiencing this issue or found a way around it? If there is something in our code that we can alter to keep this from happening I would love to know about it, as we spend time and resources troubleshooting and resolving an issue that doesn't exist until a Windows update runs and our application becomes un-usable until resolved.
I encounter this error as mention in the subject line. I just change from windows XP 32 bits to windows 7 64 bits, and the following code were working fine in windows XP, but in windows 7 I get ambiguous namespace for all the DIM cnn As New ADODB.Connection and DIM rst As New ADODB.Recordset.I Have no idea what is going on.However, the exe that is created from my old XP runs fine on both XP and Windows 7 32 bits but not the Win7 64 bits.
Public Sub mStartConnection() Dim initPath As String Dim File_Reader As StreamReader Try
Using Visual Studio 8. On old computer, my application works. When installed on a new computer I get an error message:
Line of code causing error: Dim WordApp As New Microsoft.Office.Interop.Word.Application
Error message: Error 103 'Application' is ambiguous in the namespace
Both computers reference:
C:WindowsassemblyGACMicrosoft.Office.Interop.Outlook12.0.0.0__71e9bce111e9429cMicrosoft.Office.Interop.Outlook.dll Old computer is 32 bit XP. New computer is 64 bit Windows 7.
I am currently programming a complicated inheritance structure for an Insurance Application. One DLL has classes that can be used and inherited from. DLL Two has Classes specific for our Auto Line of business, however when i attempt to use Object 2 from a Web Application it errors out because one of the classes is ambiguous because it appears that DLL Two inherits a class from DLL One which appears to pull in the entire inherited class. Since the Web app has a reference to both DLL One and Two, One has the class, Two seems to also have it and so compilation errors out with an ambiguous class in the same namespace.
To attempt to get more specific ill try a quick run down.DLL One - PGPolicy.dll contains standard classes with properties and methods needed for every line of business such as:
Policy, Name, NamedInsured, Unit DLL Two - PGPolicyAuto.dll contains the following Auto specific classes: Vehicle Inherits from Unit Driver Inherits from Name
Since PGPolicy.dll contains classes needed by all lines of business and PGPolicyAuto.dll has more specific classes for the Auto line of business, the web application references both of them. The problem is that since Driver inherits the Name class, it appears to create a Name class in the same name space that the PGPolicy.dll has the namespace in, which gives me an Ambiguous class "Name" in the PG.Policy Namespace.
