I have two .NET projects in the same domain. The first project I create long time ago in VB.NET. Now I create another project that I built in C#. How can I set up my new project in the same domain so I can access the new forms that I built in C#. Do I need to submit the whole folder from the project? Do I need to change anything in the web.config? Right now I am getting this error. [PhoneControl] is the new project in C#.
http://www.martinesexpress-inc.com/PhoneControl/Default.aspx
If you look in the error page it says:
alt text http://img246.imageshack.us/img246/5868/capturevv.png
Version Information: Microsoft .NET Framework Version:1.1.4322.2407;
ASP.NET Version:1.1.4322.2407
And you are trying to use some .NET 3.5 components
Change the website to use .Net 2.0 and make sure the server have .NET 3.5 SP1 installed
If you are using IIS6:
alt text http://img185.imageshack.us/img185/1410/capture2s.png
You're declaring the language correctly in your page?
Related
I am creating a Console Application in Visual Basic. I would like to use features like My.Computer.FileSystem like I would in Windows Forms but it is unreferenced in my project.
After a bit of googling, I came across this namespace called Microsoft.VisualBasic.MyServices which appears to contain things like FileSystem which I am unable to access with my Console Application
I have tried referencing a few different libraries that I found in COM Components, but none appear to include MyServices
I know this is possible because I used to be able to do this when I worked with Console Applications a few years ago.
Any help would be appreciated.
Thanks.
I have tested to confirm and, using VS 2019, the My namespace is supported as usual in a VB Console Application project targeting .NET Framework 4.8 but it is not supported in a similar project targeting .NET Core 3.1. I'm not sure what the situation will be in .NET 5 but, for now, stick with .NET Framework or forgo the My namespace.
I'm not new to programming, but am new to Microsoft-centric technologies. In this case, I have downloaded Visual Studio 2019 Community edition and am trying to get some stuff working as a VBA Console application.
Here is the link the the Visual Basic Guide I am using as documentation:
https://opdhsblobprod02.blob.core.windows.net/contents/c6aea4f5457448ee818b7292ba695982/8f8c9552565899a6bd5ea3443dc48752?sv=2015-04-05&sr=b&sig=z6HVPKMrsWrYMl1xp9Pk34R040%2B8A71q3nmRLNTG6lk%3D&st=2019-10-18T21%3A16%3A48Z&se=2019-10-19T21%3A26%3A48Z&sp=r
On Page #1 of that guide is a section titled "Development with My". 'My' can have various pieces, depending on the project type. In this case, my project type is: Console Application (from VS, File -> New -> Project, select: Console App (.NET Core) )
On page 59 of that guide is a table that explicitly shows which different parts of 'My' would be available in different project types. For a Console App, all of My.User, My.Resources, My.Setting should be available (as well as some other things).
Yet within my VBA code, the editor implies that the only part of 'My' available is a My.InternalXmlHelper. (I guess that comes by default - I haven't done anything to explicitly try to add such a thing.)
Obviously, some piece of the puzzle is missing here that enables access to all this wonder 'My' functionality that is described. Anybody know what needs to be done here so that my VS environment knows about My.User (and other stuff)?
Thanks.
.NET Core is a different beast altogether, in addition to the other languages you seem to be mixing together.
Based on this link, VB My namespace support is not a part of core 3.0. I'm not sure if it's in earlier core versions, because I haven't been working with VB in Core.
A large part of what makes Visual Basic special is the Visual Basic Runtime. .NET Core 2 contains only the small part of Visual Basic Runtime that is defined in the Visual Basic Language Specification which was initially designed for interop with phones.
The major effort for Visual Basic 16.0 will be moving the Visual Basic Runtime to .NET Core 3.0 to provide expected features like Mid or the My namespace. This work will probably not be ready for the first preview of .NET Core 3.0 but will appear in a later preview.
I think the guide you are working with is for .NET Framework 4.x and earlier (Core is a different initiative that involves getting .NET to run on multiple Operating Systems, etc.). Try creating a new .NET Framework app. The templates will have (.NET Framework) in the name, e.g., ASP.NET Web Application (.NET Framework).
I have a bit of an awkward scenario (I think). I have a Asp.Net UserControl in a project which targets the 4.0 framework and also uses a 3rd party dll (Telerik controls).
I tried using vs2010 to copy the usercontrol and required references to the Visual Webpart within an Empty Sharepoint (2010) project. But it will not allow the references to dlls which in turn, reference the 4.0 framework etc.
So my question... is it possible to do this? If so, the steps in a bit of detail would be VERY appreciated.
thanks,
KS
If your third party dll is for .net 3.5 then you can use the dll and use the user control in a same way the smartPart project loads or you can just use the smartpart web part.
But you can not use .net version 4 assembly in sharepoint 2010. SP2010 is targeted for .net 3.5 and only can use assemblies with version 3.5 and before.
The reason you could test the smartpart environment is most probably because you didn't import any dll's targeted for .net 4 or none of the methods included in the uc were from .net 3.5.
Sharepoint 2010 .net version so question here.
I'd like to use ELMAH in an ASP.NET MVC 2 application running on .NET 4, but according to the project hosting site on Google code, it only supports .NET 1.1 and 2.0.
Is there a .NET 4 version of ELMAH already, or do I have to download the source and update whatever breaks myself?
Elmah works perfectly fine for ASP.NET 4.0.
However, there are a few tricks in getting it setup to work perfectly on an MVC website.
I have recently starting blogging about this topic so be sure to check out my blog series on logging in MVC. The first article covers getting Elmah set up and running for MVC using all the tricks that you can find about it on StackOverflow.
There is a link to downloadable code at the end of the article. Hope that helps.
http://dotnetdarren.wordpress.com/
I am using .NET 4.0 and I dont about a new version.... but I am using the elmah 1.1 and it works....:)..You may have to change source though to add custom fields or log additional values..which is bit of a pain...but get started here
Well it's open source nothing should prevent you from recompiling it using the .NET 4.0 framework.
This link has some information about running pre .NET4 web apps and .NET4 web apps in a server.
EDIT:
Actually you won't need to recompile ELMAH. According to this and this article the In-Process side by side execution should do the trick.
I had the same question so I downloaded the 1.1 src, opened it up in visual studio 2010, changed the project to target 4.0 and rebuilt it. I then dropped the dll in my ASP.NET MVC 2.0 app and it has worked fine.
How can I create a VB application in VS2008 without requiring the application be run on a computer with a .NET framework in place?
You can't create a non-managed VB application in VS 2008.
You would have to use C/C++ or go back to VS 6.
You can look at the question below for more information on .NET linkers. That is technically an option, but if I were starting a new application that I didn't want to depend on the .NET framework I would not use a managed language.
Running .net based application without .net framework
You'll need to use a 3rd party .NET linker, Visual Studio itself doesn't support what you're after but a number of tools allow it to be done.
A couple of tools:
Remotesoft Salamander .NET Linker
Xenocode app virtualization
Another, non-VS, option is to use Mono to build a "Bundle" which combines both the runtime and your application into a single executable:
Mono:Runtime - Bundles
You can't. You would need to go back to Visual Studio 6 and create a VB6 app.
You can't. VB is .net based, there isn't a non .net VB anymore.
The best you can do is include the .net redistributable with your application's installation.