Is it .vb like the latest version, I'm talking about version 6.0 (classic)? I'm trying to properly title a visual basic script for a module I need. If I have to redo a script because I cannot name a extension I am going to be mad.
There are several:
.cls (class file)
.frm (form)
.frx (form - binary information)
.ctl (custom control)
.ctx (custom control binary information)
.vbp (project)
.vbg (project group)
.bas (module)
Probably more...
The one you want is most likely .cls.
This answer as also good definitions:
https://stackoverflow.com/a/4385921/755977
From the documentation:
Project File Extensions
Visual Basic produces a number of files when you create and compile a project. These can be categorized as
follows: design-time, miscellaneous development, and run-time.
Design time files are the building blocks of your project: basic
modules (.bas) and form modules (.frm), for example.
Miscellaneous files are produced by various processes and functions of
the Visual Basic development environment: Package and Deployment
Wizard dependency files (.dep), for example.
Design-time and Miscellaneous Files
The following table lists all the design-time and miscellaneous other files that may be produced
when you develop an application:
TABLE 1 (Extension, Description)
.bas Basic module
.cls Class module
.ctl User Control file
.ctx User Control binary file
.dca Active Designer cache
.ddf Package and Deployment Wizard CAB information file
.dep Package and Deployment Wizard dependency file
.dob ActiveX document form file
.dox ActiveX document binary form file
.dsr Active Designer file
.dsx Active Designer binary file
.dws Deployment wizard script file
.frm Form file
.frx Binary form file
.log Log file for load errors
.oca Control TypeLib cache file
.pag Property page file
.pgx Binary property page file
.res Resource file
.tlb Remote Automation TypeLib file
.vbg Visual Basic group project file
.vbl Control licensing file
.vbp Visual Basic project file
.vbr Remote Automation registration file
.vbw Visual Basic project workspace file
.vbz Wizard launch file
.wct WebClass HTML template
Run-Time Files
When you compile your application, all the necessary design-time files are included in the run-time executable files.
Run-time files are listed in the following table:
TABLE 2 (Extension, Description)
.dll In-process ActiveX component
.exe Executable file or ActiveX component
.ocx ActiveX control
.vbd ActiveX document state file
.wct WebClass HTML template
In addition I have seen .vbi used as an "include" file. Basically a .bas module. I'm not sure how common this practice is.
Related
In short: When building a VSIX project In Visual Studio 2015, the build process is attempting to load random files (such as icons, .config files, .targets file) as if they were .Net assemblies.
I am attempting to build a VSIX project that includes a referenced project template and a embedded wizard assembly. I've done the exact same thing previously with success, following the steps described at How to: Use Wizards with Project Templates.
This time, however, when I attempt to build the VSIX project I get bizarre errors such as the following:
Could not determine the FullName of the Assembly at "C:\Source\VSTS\Toolkits\v7\Web.Site\v7.2\packages\Microsoft.Net.Compilers.1.3.2\tools\csc.exe.config". Could not load file or assembly 'csc.exe.config' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Note, the compiler is trying to load a config file as if it were an assembly. In fact, I first got this error when it was attempting to load the icon file for the VSIX...as if it were an assembly. If I rename or remove the file in the error message and rebuild I just get the same error but with the next random not-an-assembly file that the compiler encounters.
Why is the compiler attempting to load random files as if they were assemblies? How can I make it stop so that I can actually build my VSIX project?
More info:
This error is thrown by the DetokenizeVsizManifestSource build step defined in Microsoft.VsSDK.targets:
<DetokenizeVsixManifestSource
InputFile="#(SourceVsixManifest)"
OutputFile="$(IntermediateVsixManifest)"
ResolvedReferences="#(_VsixManifestResolvedReferences)">
<Output TaskParameter="OutputFile" ItemName="FileWrites" />
</DetokenizeVsixManifestSource>
I had the same problem. It seems you can't add add an applciation to a VSIX. You need the project to output a dll and attach that.
If you need to attach an application try to do so as File not as Project.
I just discovered a misterious file in my (new) Visual Studio 2012 C++/CLI project: app.aps.
I can find no reference on the internet about it. What is it meant for? Can I safely delete it? It seems so. Should I ignore or include in my commits to source version control?
It's a generated file for designer efficiency, you can ignore it in source control:
File created by Microsoft Visual C++, a software development application; stores the binary representation of a resource included with the project; enables the application to load resources more quickly.
http://fileinfo.com/extension/aps
APS files are the binary versions of resource files. As resource editor does not directly read the .rc and resource.h files, the resource compiler turns them into the APS file.
Reference - Files Affected by Resource Editing
I am using Visual Studio 2012 to create a class library project that will also include a number of TypeScript (.ts) files, as well as their generated .js and .js.map files. All of these files need to be included in the assembly as embedded resources, so that they can be exposed to a consuming ASP.NET MVC application via a custom VirtualPathProvider.
Note: although only the generated JavaScript files are essential for the production environment, the .ts and .js.map files must also be accessible to the web application, for debugging.
This presents a conflict, since TypeScript files are usually assigned the TypeScriptCompile build action but I also need them to be assigned EmbeddedResource.
Is there any way to assign multiple build actions to a VisualStudio project component? Alternatively, is there another way to get TypeScript to compile files that are not explicitly marked as TypeScriptCompile or to get Visual Studio to embed files that are not marked as EmbeddedResource?
Thanks for your suggestions,
Tim
If you had a TypeScript file that referenced all of the others, only it would need to have the TypeScriptCompile type as the compiler should walk all the dependencies and compile all the rest too.
So creating a file that acts as the compilation target and that references all of your other files might allow you to change all the rest to EmbeddedResource.
I have 2 copies of a solution, each of which is compiled against a different version of the same 3rd party API and a different .NET framework version.
Solution A - compiled against v2012 of a 3rd party API and .NET 4.0
Solution B - compiled against v2011 of a 3rd party API and .NET 3.5
Solution A contains all the source files and Solution B links to these files (using "Add as Link" in Visual Studio).
Conditional compilation is used to include code that is specific to one solution or the other.
My solution contains some XAML (WPF Windows, User Controls & Resource Dictionaries). Solution B links to these XAML files and compiles ok, but when I run it I get a Set property 'System.Windows.ResourceDictionary.Source' threw an exception exception.
I've Reflectored over both versions of the assembly and there are differences in the resource names.
For example, one project contains a Windows/MyWindow.xaml file and the compiled assembly from Solution A contains a windows/mywindow.baml resource, while in the assembly from Solution B the name of the resource is just mywindow.baml.
Is there a way to compile the same XAML file into multiple projects?
if you are on Windows7/Vista/2008 (not XP), maybe try using Windows link not a Visual Studio Link.
http://technet.microsoft.com/en-us/library/cc753194(v=ws.10).aspx
So with a Windows link, it is the same file on disk, but appear as separate files in each project directory. (Yes, changing the file in either location changes it in both locations because the file is really in one location with a pointer in two locations)
I've created a DLL to a project in Visual Studio 2010.
I'm using this DLL in another project. Using the functions is completely possible - but I can't see any tooltip.
In addition - if I'm in the same project the tooltips can be seen.
I've read some issues about using the XML file with the name of the DLL in the 2nd project, but I'm afraid I don't have any XML file (as far as I see...).
I'll appreciate your help!
Lior
In the project settings of your DLL you can specify that a XML file will be created each time the assembly is build. Thi setting is located on the "Build" tab, region "Output" and is called "XML documentation file". Mark the checkbox in front and the xml file will be created.
When you use the dll in another project you have to copy the xml file along with the assembly file to have the IntelliSense information in place.