Here's a dialog box which runs for approximately 16 projects and takes over 5 minutes to complete (in total).
Can anyone tell me what it's doing and how to make it stop?
I discovered the answer, thanks to Alexandre DeFalque.
VB is converting old VB6 modules(modulename.vb) into static classes for use by .NET. This can take quite a while.
I had previously scoured the Internet looking for an answer to this; hopefully someone else has now been saved that bother.
Related
I recently programmed a Windows Form Application on one laptop, however, when I attempt to run the executable on my client's PC it won't open. There are no error messages generated, it just won't open.
The only thing in use that wasn't built into VS2015 was Telerik UI for winforms and the application is a standalone exe.
Any suggestions?
I finally got this sorted a couple of days ago. After a LOT of fiddling about I realised that it was indeed to do with the references. After consulting the Telerik Documentation (as Chris suggested) I realised that, indeed, the dlls were stored in the GAC (something I'd never heard of) and not actually automatically packaged with the software. So I editted the program file options so that they were included and problem solved! Thank You all for your help and sorry the original question was so badly written, I had no idea what data it would have been relevant to include
One of my duties at my job is to enhance and maintain a mature VB.Net windows application used internally by my company. We run 8 computers at the small company that each runs the app with no problems.
Recently we replaced one of the computers with a pretty standard notebook running Win 7 Professional with SP1 and for some reason, it won't display message boxes displayed using the normal MessageBox.Show("Message") method.
The vendor who sold us the computer says it must be the program, and I kind of sympathize with that view, but the fact is we have 8 other computers that all display their message boxes just fine.
Thought I'd post the issue here to see if anyone else has run into this and, if so, did they find a resolution?
I'm going to paint outside the lines a little bit and answer my own question with sort of a non-answer.
We battled that computer for about a week and a half and finally gave up and reinstalled the OS. Problem solved. Not really an answer because we still don't know what was going on or why reinstalling the OS fixed it.
Reinstalling was really an act of frustration/desperation as much as anything else. In the end we were just thankful the problem went away and we could move on. Figured I'd get this off of the unanswered questions list since I'm not really waiting for or expecting an answer at this point.
Ok bear with me because i am frustrated beyond belief right now.
go back about 30 minutes ago, i create a VB windows forms application. cool, nothing out of the ordinary only i make a big mistake and decide to start again. so i close the solution, delete the project folder and go to start again, only now i'm presented with
"requested operation cant be performed on file with user-mapped section open"
ok i think, there's obviously something still reading it or whatever, so i close VS completely and restart.. no avail. log off and try again. nothing. restart the computer. still nothing. what is causing this issue? i can create a C# Windows Forms Application without a frigging problem. everything BUT a VB WFA. what do i do? i'm in no real position to re-install VS right now or i'd have started 20 minutes ago. i really need a helping hand here please
Hey there I was wondering if anyone had a solution to the problem I am having when programming in Microsoft Visual Studio with VB.NET.
Basically I want to know how to load images on a form faster. I am creating a 1 form design of a program and whenever I use too many images, it takes >20 seconds to load and becomes really slow. I was looking to see if anyone has managed to find a work around around this however I can't seem to find one.
Any help would be greatly appreciated :)
I would like to hear of the experiences of classic vb developers who migrated their applications to delphi rather than vb.net. How has it worked out? Are you glad or sorry that you didn't move to vb.net?
I am not really a vb developer but rather a Delphi developer who was forced to maintain some vb apps for a while. I tried to migrate one vb app to vb.net and after that experience I never tried it again. I successfully migrated several vb apps to Delphi. It wasn't easy and it became a pain in the lower back to find native Delphi replacements for some of the OCXes that had been used (I will never again rely on a third party library for which I do not have the source code.), but it worked out OK.
But as said above: I am an experienced Delphi developer, so I didn't have to learn Delphi at the same time as migrating a vb app. That certainly made it much easier.
I just spotted this on DelphiFeeds:
Delphi for Visual Basic developers
Help to migrate VB applications (knowledge and skills) to Delphi
I had a good friend who moved from Classic VB to Delphi a while ago (back before .NET). He was really happy with the move.
The company he worked for made applications in VB, and they put together a special team (2 developers) to create Active X controls in Delphi for the rest of the company to use. Additionally, when there was something that they couldn't do in VB then the Delphi team would do it. That was when he was introduced to Delphi.
He said it didn't take long before the Delphi team could prototype applications in Delphi faster then the rest of the development group (he never said how large, but way more then two) could. The company never made the switch to Delphi from VB because someone was under the impression the VB was a better solution despite the evidence that Delphi was more powerful and faster.
A few years are I was working with another student on our placement year. We worked for a very large manufacturing company. One of his projects was to create a classic VB app to interface with multiple cameras on a production line and analyse the data in real time. In classic VB this was a shambles - it took on average 1.5 minutes to process a single frame from a single camera (7 cameras at 24 fps) there was no that he could optimise it.
He eventually took the plunge in to Delphi and re-written that app and works fantastically. I've recently been in contact with a few friends who still work there and his app is been running smoothly for 3 years now.
I've worked in both VB and Delphi, and Delphi is (IMO) much less frustrating/limiting. You should be able to use ActiveX / OCX controls as needed (though I agree w/other comments re: avoiding there where you can, and being sure ot have full source code). Apps we've migrated from VB to Delphi (two) have gone well.
I did try in two instance to migrate from VB to Delphi but unfortunately I had to abort midway in one app as it used a lot of third party ActiveX (most from ComponentOne and a few from CodeJoke). We had to abort midway as we could not find any VCL components having equivalent functionality to the ActiveX used in the project.
It was a nightmare for us. Thank god we aborted midway and switched to C#. It was unbelievable that we could get all the features in .NET component to the ditto!
The app we managed to convert, went well off but we had to get rid of a few features that we had implemented in the original software as they required more work in Delphi.