VS2010 Complaining About Microsoft.VisualBasic Dependency?
Feb 6, 2012
I've got a .NET solution that I've just upgraded from VS2008 to VS2010. It contains three web projects and two straight VB projects. The web projects all depend on (and have a reference to) one of the VB projects called BusinessLogic.All projects are targeted at .NET 2.0, but VS2010 is raising the following build warning:
The following assembly has dependencies on a version of the .NET Framework that is higher than the target and might not load correctly during runtime causing a failure: BusinessLogic, Version=1.0.4419.22315, Culture=neutral, PublicKeyToken=null. The dependencies are: Microsoft.VisualBasic, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. You should either ensure that the dependent assembly is correct for the target framework, or ensure that the target framework you are addressing is that of the dependent assembly.
So I'm guessing it has something to do with the fact that I don't have office loaded on my computer. Now I have another laptop, with office that I loaded this project on, and it works fine. So do I have to load office on this computer, or can I just reference something?
I am almost done cleaning the code. It is a huge project and I only have 35 errors left. I have opened a new thread as this is no longer only about IsNumeric. All errors relate to the following Microsoft.VisualBasic keywords:
I have a method which takes a stored procedure name and a Microsoft.VisualBasic.Collection? I am referencing a vb project in which I have to pass in a collection to this method, but the current project I am in is in c#, so I am unclear what I can pass into the method?
Here is the vb call:
public void CallStoredProc(string spName, Microsoft.VisualBasic.Collection params);
In my c# app, I need to call this an pass in the appropriate c# object to params.
I am trying to use my .NET DLL library that is compiled in VIsual Studio 2008 in Linux. Now for that they have this Mono CLI implementation but unfotunately they have not fully implemented Microsoft.VisualBasic library as of yet. So when i try to call certain methods from my DLL i get this error: "Could not load file or assembly 'Microsoft.VisualBasic, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.".
But not every function in my DLL crashes with this error. I found out that it is because this error only occurs when i use VisualBasic functionality. But the problem is that many things that come from this library are default things that you can do when using VB .NET.
Is there any way i can completely remove VIsualBasic functionality from my code in my DLL library?
I read in another post that setting Option Strict On is a good place to start but i still get the error even after doing that. Additionaly, i have unchecked VisualBasic namespace and removed it from references.
I want to get this Assembly version, I have an old application and lost the source code. When I try to disassemble with reflect it ask for Microsoft.VisualBasic Version=7.0.3300.0 Where I can find it?
I use VS 2008, .net 3.5, C# projects. I need do the same functionally like Microsoft.VisualBasic.FileIO.File System.DeleteDirectory. Anyone says referencing the Microsoft.VisualBasic is often undesirable from within C#. Any association with VB from within C# code strikes me as undesirable. Using FileSystem class, this is a perfectly fine solution, but I prefer not references Microsoft.VisualBasic library. That one I would avoid.
When I start my application I get the following error:
method not found microsoft.visualbasic.msgboxresult
I have tried repairing my .NET installation.
Note: This error only occurs on one machine. On every other machine it works fine which makes me think something with the .NET assemblies was corrupted. It was working fine on the broken machine a few days ago.
When ever I start a blank WPF project in Visual Basic 2010 (SP1) I get the following error:
Type 'Microsoft.VisualBasic.CompilerServices.DesignerGenerated' is not defined.
The error comes from the auto-generated code in MainWindow.g.i.vb - when I try to add a reference to Microsoft.VisualBasic, it says I can't because it will be added at runtime.
I want to see the source code of Microsoft.Visualbasic.Financial.IRR how would i break it and how would i seee the sorce code of IRR method of financial class?System{" df -k | awk '{sum += $4 }i; END {print sum} '"};
above line is not useful I've tried to view it using different software but it will not work for me is there any software that will view it source code.
I'm having trouble with a more complex program, so I've created a simple program to highlight my issue (see code block below). When I declare a Collection generically (like I have below) and try to call IndexOf, I get the following compiler error:
'IndexOf' is not a member of 'Microsoft.VisualBasic.Collection'. (BC30456)
If I instead declare my Collection as a collection of strings (Public mycollection As New Collection(Of String)), I then have access to the usual methods, but the .Add method then only allows a single string to be passed to it. This means that I can't use a key, which seems to be the point of a collection. Is there any way to have a general, keyed collection that can use IndexOf?
Imports System Imports System.Collections Imports System.Collections.Generic Imports System.Collections.ObjectModel
I'm a beginner to Visual Basic. In here I want to recreate a piggy bank which tells me how much money do I have. I created a function but the program tells me :
I developed one application in VB.Net 2010. It worked fine on my laptop. Now when I run this on another PC, it just crashes and give windows error as below.
[CODE]..........................
Along with this.
[CODE]......................
This application required .Net framework 4 & Oracle 9 ODBC drivers, which I installed on new PC.
I am not able to figure out what is the problem exactly, however it seems something with .Net framework itself.
I seemed to have have ruined my settings on VS 2010... I can't get the Shapes to work just after I had fixed the problem with the PowerPacks, and then it deleted all of my shapes I had on my form after I was tweaking the code and added another shape. And ever since, the shapes make errors and I can't change there colors. I've tried reinstalling VS 2010, and changing refferences doesn't work anymore. The title is the problem I have with trying to add a shape through the code in my project, here is the code for that:
Public Class Form1 Public Circle As New Microsoft.VisualBasic.PowerPacks.OvalShape() Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
I have a large project where we have 2-3 dll projects that are converted from VB6 to VB.NET. We have fixed all the issues that caused compilation errors, and most of obvious issues in running, so now we have basically a program up and running. The exe is created from scratch in VB.NET, using a lot of functionality from the converted dll's (including GUI forms). What I wonder is when I run the program in debug mode, I get a bunch of warnings in the "Immediate Window" saying:
A first chance exception of type 'System.Exception' occurred in Microsoft.VisualBasic.dll
...and some of other type (but most of them in Microsoft.VisualBasic.dll).I was wondering if this is common in projects converted from VB6, or if it is caused by bad design in our code...
I now have SQL Parameters set up and I'm using them to save/delete/add my data. This all works well, except when it's trying to save a combobox to the datatable it appears with the error above.Majority of my comboboxes have datasources, and the valuemembers of these are the actual list items, not the ID's of the list items.I'm not sure why this error could be happening, I'm fairly sure I've connected everything to the binding source correctly; I've checked it a few times.Does anybody know what the cause of this could be? I've looked around a bit and I haven't found much
i used printForm to print forms, but when i installed the powerpack 3.0 it doesn't work anymore.i am always getting an error "PrintForm is ambiguous in the namespace 'Microsoft.VisualBasic.PowerPacks.Printing'" i am using visual studio 2008 professional edition.
I've started to use a Vista machine for development. In case it is significant: I'm using MSBee so that I can code in the Visual Studio 2005 IDE while still building against the 1.1 framework.On the Vista machine, when I tried to build a particular vb project, I got this error:
error BC30464: Namespace or type'Compatibility' in the project-level Imports 'Microsoft.VisualBasic.Compatibility' cannot be found.
The same project built fine on my old XP machine. I checked in this folder on my Vista machine:
C:windowsmicrosoft.netFrameworkv1.1.4322
...and sure enough, "Microsoft.VisualBasic.Compatibility.dll" was missing. So was "Microsoft.VisualBasic.Compatibility.Data.dll". Copying them from my XP machine to my Vista machine allowed me to build the project successfully.I'm just a bit puzzled as to why this happened. Why was "Microsoft.VisualBasic.Compatibility.dll" missing? I'm also not very comfortable with my chosen solution - copying the DLL manually. It works, but surely there must be a better way.
I am using Microsoft.VisualBasic.Fileio.TextFieldParser to parse a CSV file that was created with Excel 2003. The parser is working great with the exception that it is converting extended ascii values to question marks! So if the file content was:
± 3 The TextFieldParser is returning ? 3
I have tried all of the encodings in the System.Text.Encoding package with no luck. I thought I had it with UTF7 but it was dropping other characters like replacing the + sign with a space.
When running code analysis on my project, I receive the following message:
CA1051 : Microsoft.Design : Because field 'ClassName.VarName' is visible outside of its declaring type, change its accessibility to private and add a property, with the same accessibility as the field has currently, to provide access to it.
Public VarName As String to this:Public Property VarName As String
I don't understand why the Property keyword is so important in this particular case. Can anyone provide an explanation as to why changing this member to a Property makes a significant difference to code analysis?
i have 2 windows machines with VB 2008 installed on both. I created a windows app on 1 machine and put the powerpacks dll file with the app folder anyway. For some reason, when i load the project up on my other machine, i just get a never ending list of errors related to PowerPacks. Why? I have exactly the same version installed and tried download the PowerPacks on Windows website. I just get over 102 errors saying Type 'Microsoft.VisualBasic.PowerPacks.LineShape' is not defined. Anyone care to enlighten me?
