Jimbo99999
asked on
Vb.Net - Post Conversion Upgrade Warnings
Good Day Experts!
I have my VB6 project upgraded to VB.Net 2005 with the help of FernandoSoto. I only had 1 error at the bottom of my VB.Net editor and I was able to resolve it without much trouble.
However, I have many warnings within my code from the conversion process as below...
"UPGRADE_WARNING: Couldn't resolve default property of object..."
There are no "blue squiggly" error lines under the code that each of these UPGRADE_WARNINGS are referring to.
Since there are no errors, do I have to do anything with these? If so, in general what do I have to do with them?
Thanks,
jimbo99999
I have my VB6 project upgraded to VB.Net 2005 with the help of FernandoSoto. I only had 1 error at the bottom of my VB.Net editor and I was able to resolve it without much trouble.
However, I have many warnings within my code from the conversion process as below...
"UPGRADE_WARNING: Couldn't resolve default property of object..."
There are no "blue squiggly" error lines under the code that each of these UPGRADE_WARNINGS are referring to.
Since there are no errors, do I have to do anything with these? If so, in general what do I have to do with them?
Thanks,
jimbo99999
ASKER
Thanks for responding Fernando.
Ok, I checked out your link but that was not the scenario with the textbox that I have here.
But it made me think...if I may run this by you. Most of the issues have .Value at the end.
Here is an example:
Dim ShipFromZip As Object
ShipFromZip = rs.Fields("shipfromzip").V alue
When I take the .Value off the end, intellisense provides Value as a valid selection. So I am not sure what it is barking at.
Here is another example:
Dim d As mshtml.HTMLDocument
d.body.all("txtName").Valu e = "User"
When I take the .Value off the end, intellisense does not provide Value as a valid selection. So I am not why it is not giving me an error or even if that is why the UPGRADE_WARNING is present.
Thanks,
jimbo99999
Ok, I checked out your link but that was not the scenario with the textbox that I have here.
But it made me think...if I may run this by you. Most of the issues have .Value at the end.
Here is an example:
Dim ShipFromZip As Object
ShipFromZip = rs.Fields("shipfromzip").V
When I take the .Value off the end, intellisense provides Value as a valid selection. So I am not sure what it is barking at.
Here is another example:
Dim d As mshtml.HTMLDocument
d.body.all("txtName").Valu
When I take the .Value off the end, intellisense does not provide Value as a valid selection. So I am not why it is not giving me an error or even if that is why the UPGRADE_WARNING is present.
Thanks,
jimbo99999
Hi jimbo99999;
In this statement, "ShipFromZip = rs.Fields("shipfromzip").V alue", what is the type of object of rs?
In this statement, "d.body.all("txtName").Val ue = "User"", the object d being an object HTMLDocument the method body should return the document body but I am not sure what the method All("txtName") does. In .Net properties are usually called Text and Not Value.
In this statement, "ShipFromZip = rs.Fields("shipfromzip").V
In this statement, "d.body.all("txtName").Val
ASKER
Dim rs As ADODB.Recordset
Dim ShipFromZip As Object
ShipFromZip = rs.Fields("shipfromzip").V alue
This is up at the top of the project:
Imports VB = Microsoft.VisualBasic
I did not put it there. Does that mean I can keep using the rs recordset?
Dim ShipFromZip As Object
ShipFromZip = rs.Fields("shipfromzip").V
This is up at the top of the project:
Imports VB = Microsoft.VisualBasic
I did not put it there. Does that mean I can keep using the rs recordset?
Hi jimbo99999;
Warnings will not stop a program from compiling. They are just that warnings to be aware of that might cause an issue. In this code you might get rid of the warning by changing the code as follows.
Warnings will not stop a program from compiling. They are just that warnings to be aware of that might cause an issue. In this code you might get rid of the warning by changing the code as follows.
' From this
Dim rs As ADODB.Recordset
Dim ShipFromZip As Object
ShipFromZip = rs.Fields("shipfromzip").Value
' To This
Dim rs As ADODB.Recordset
Dim ShipFromZip As String
ShipFromZip = CType(rs.Fields("shipfromzip").Value, String)
Also you asked about this, Imports VB = Microsoft.VisualBasic, yes you do need this. some of the objects that were converted to .Net lives in that name space and if it were not there you would get errors ending with "are you missing a namespace or reference".
ASKER
Excellent information...thanks.
I was looking at the original VB6 project and found something interesting.
The original --> Dim ShipFromZip
The converted--> Dim ShipFromZip As Object
What type is no type in VB6 in VB.Net?
Is that why you made it a string?
Good stuff here...not my forte but learning quite a bit.
jimbo99999
I was looking at the original VB6 project and found something interesting.
The original --> Dim ShipFromZip
The converted--> Dim ShipFromZip As Object
What type is no type in VB6 in VB.Net?
Is that why you made it a string?
Good stuff here...not my forte but learning quite a bit.
jimbo99999
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Try and see if this this the cause of the "UPGRADE_WARNING" in the project.
Late-bound default property reference could not be resolved