One method to build dlls from VIs is to right click the "build specification" in the project window -> new -> Shared Library (DLL). This has worked for me on other Labview installations, but not on my student edition.
Is there an alternative/extra step/installation I need to know about to build dlls from the student edition of Labview or is this functionality not available in the student edition?
The Student Edition, like the Full Development System, does NOT include the Application Builder which you need to create DLLs - Jakub has misread the NI page.
You either need the Professional Development System, or the Application Builder as an add-on to one of the other versions.
According to NI LabVIEW Student Edition page, it's got "Same functionality as LabVIEW Full Development System", which supports DLL builds, so it doesn't seem to be an edition issue.
UPDATE: See #nekomatic response.
Related
I installed VS 2022 Community and am trying to work on a project that was developed on VS 2008 Pro. VS is giving me this report:
How do I force VS to make whatever upgrades it needs in order to run this program? I can provide more info if needed.
MS in their wisdom, dropped support for the Setup & Deployment project, can't remember when exactly, then after a bit of an uproar re-instated it through the Visual Studio marketplace https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.MicrosoftVisualStudio2017InstallerProjects
Since your project has a file .vddproj, it might be a Smart Device CAB project.
It is not supported by later versions of visual studio.
It is recommended that you open it with VS2008.
I have no idea/experience in VB programming. One of my client bought me his old project which need to be modified. He says it is written in Visual Basic and no idea which version.
So how can i carry ON to work with this project by identifying the version
And what other components do i require to do the programming and user interface.
I already have Visual studio 2010 with me. So can i do my work using this software or i have to go for anything else...
Any suggestions....?
Regards
ParshTest
You need to check the earlier VS version. If the project was developed in earlier version of VS, you can upgrade to VS 2010 easily but otherwise you need to get hands on specific VS version.
Similarly if the project have database functionality or crystal report or any other external dependencies, you need to check their versions. You need to install the components according to these versions. Specify your versions and i'll tell you what to use for further development.
Does windows 8 supports visual source safe (or the other way around?)
Aka, can you install visual source safe running windows 8?
My advice is, don't go closer to Visual SourceSafe than you can spit a rat. VSS has NEVER worked right. Data corruption is all too common. When I worked as an independent consultant to Microsoft in the late 1990's and spent some of my time in Redmond, I found out MS's little secret. Virtually none of the Microsoft development projects used their own VSS. Their internal source code control in the early '90s was a customized version of the old RCS file-based system. They then bought source code rights to Perforce and created a customized version of Perforce for their own use. Now, at least since Visual Studio 2012, they only officially support their own Microsoft Team Foundation Version Control (TFVC) and Git. Support for only those two has been built into VS 2012 and newer IDEs.
Again, even the Microsoft programmers joke about VSS being a "code destruction device." If you already have a honking lot of projects in VSS 6 (which IIRC was built in 1998 and discontinued in 2006), you might want to track down the upgrade to VSS 2005, which is rare, but at least "supported" to whatever degree until sometime in 2017. I also have no idea if either is compatible with Windows 10 (I've installed 6.0 on Windows 7) I'm not sure it's any better, and Microsoft makes it very hard to find full or upgrade downloads of VSS 2005 on their site, but I recall seeing a link for it on one of the MS forums. Search for it.
OTOH, if you are not welded to VSS and don't want to use either TFSC or Git, Subversion (standalone) is a very good alternative (CVS is a dead issue and is not being supported). My current client has development teams using either Git or SVN for their .NET (yuck) projects.
DISCLAIMER: My personal experience (as StackOverflow wants to see for opinion posts) covers 40 years as a top-level software design and development consultant for primarily Fortune 50 companies, during which I have used extensively just about every major COTS and open-source make utility, bug-tracker, and version-control system available. I was a primary beta-tester for the original PVCS (Polytron Version Control System), later bought by Borland. I have also written a proprietary text delta-based version control system for Dow Jones in the early '90s.
We've got it to work.
When it says you'll have to close all running program's it isn't just being nice.
Yes, and in windows 10 too.
Copy and paste VSS from other computer in any folder in new computer.
For register in VB60 ide, execute SSINT.EXE
Find an run .EXE in VSS folder for other opcions
Yes. It can be installed in Windows 10 computers too.
I recently was given control of a project that is based on the Codeblocks IDE. This project consists of large make scripts, gcc for motorola microcontrollers, and example C programs. The code is under subversion source-control, but there are no test scripts.
I am wondering what the best test package for windows based software is. I would like the ability to launch the software, open a project and compile. Then I would look in the output directory for specific files, binaries, etc. I have the ability to provision a dedicated VM to this task.
I'm wondering if there's a better way for testing than fully launching the IDE and clicking through menus.
I wish this project was assembled with Test-driven development in mind, but now I'm being forced to add in test afterwards.
Thanks for any advice u might have
IMO, you need Microsoft Visual Studio 2010 bundle.
Microsoft Test Manager 2010 for test case/test script/defect tracing management system, even more, you could use it as testing environment management system, including virtual machine(Hyper-V).
And you could also use the Visual Studio as the team project management tool, it has some build-in template for different agile project type.
You could get more information from MSDN.
You should get a try at this bundle,
I am looking into tools such as eggPlant. Unfortunatly this tool costs $6000. I cannot afford this right now so I am still not sure of the answer. Thanks for your input tho.
Hopefully this is a simple question and I have just overlooked something somewhere...
I am writing VB.NET stuff in VS2010 on Windows 7 64-bit. It seems to build by default for a 32-bit target, how to I tell it to make a 64-bit executable?
I went to the project properties -> Compiler -> Advanced, but don't see the option anywhere.
Oh, and this is VS2010 Express, to be clear.
This involves using the Configuration Manager, it's not a part of the project properties.
Go to the Build Menu, then click Configuration Manager. Under Active solution platform, click New, then add one with x64 as the platform. Use this platform to compile for x64.
It seems that you have to go to Build -> Configuration Manager and create a new solution platform from the Active Solution Platform dropdown and select x64 as the new platform. That will also change your Active Platform to x64 from x86.
Damn, but Visual Basic will never cease to surprise me! Or is this the Principle of Least Surprise, VB edition: VB will surprise you when you least expect it!