As of the latest release a solution containing a windows form project no longer shows a windows forms control library in the same solution in the ToolBox.
Here is a sample of the problem. It's a solution with two projects, one is a windows Form Project (called "DemoApp") and a Winforms Control Library Project (called "Brooklyn"), this is a mock up so there is only a blank form and a single control called MyButton which inherits from windows.forms.button in the control library. This was working fine until the latest VS update to 17.3. Both projects Target NET 6.0
Here's a link to the project on my Google drive. Again it's only a simple mockup to demonstrate the issue.
https://drive.google.com/drive/folders/1r2R_7N5ok0Nk4f96UUOdA3Hzzjc2Jfa1?usp=sharing
Related
I have opened VS2022 (V17.0.4) two times at the moment.
In a VB Windows Forms .net Framework project I can search in a control's property:
In a C# Windows Form .NET6 Project (Core) I cannot (there is no textbox for searching a property like in the first screenshot):
Is this search functionality indeed only availabvle in the .net Framework project or does it depend on VB or is this a setting I can set to "On" somehow?
After some investigation, it turns out that this search feature is not provided by VisualStudio, but by the DevExpress extension.
I intend to build simple Winform application just to allow user to automate their file creation and store the last filled form in a file to keep it for next run.
thus, I'm not interested in creating installer for this simple Winform application. I expected to only compile it to .exe and let it run on other computers.
I develop the application using VS2019 community with target .net 4.6.1
It won't run on computer with Windows 10 with only .net framework 4.8
We are not able to install framework 4.6.1 since it says an earlier version of .net framework is already installed.
Should I recompile my application with target .net framework 4.8?
Can't I compile my application to run on any computer which at least has 4.6.1 or newer? without installer.
(I don't really understand the .net framework backward compatibility truly mean)
my application uses:
library of user32.dll for SetForegroundWindow function
to create .ini file
Finally it works. Even compiled to target .NET 4.6.1 still work on .NET 4.8 computer actually.
The issue is because my application is targeting to another application using interope COM interface, while the license is not sufficient for the user to allow COM interface.
we notice it when we finally create a pure simple windows form, then step-by-step compiling while adding each feature.
Sorry Every Body for this silly case. And my special apologize to evry1falls for spending your time.
I'm thinking to change this Question or delete it. because it is not the issue at all
The Actual Issue is:
I created Windows Form Application starting from a blank Project. And I don't know that the .NET Unhandled Exception is not activated by default.
When created from Windows Form Project Template, the Unhandled Exception message shown.
I created another Question about it: Here
I'm working on a xamarin forms (PCL) project (A basic customer care chat app which is meant to run on Android and iOS only) that has just two xaml pages, custom renderers and few dependencies. This project is meant to be implemented into another existing project (which I don't have access to its source code) such that an action would be binded to a button on the existing app to show a page on my own project.
There is need for me to share my chat project with my client's developer but without exposing my source codes, perhaps compiling to dll or nuget package that would be added to the existing project to access my project's functions and pages. I have searched through the xamarin forum and here on stackoverflow but can't seem to lay my hands on a solution.
Is this possible at all? If yes, what am I missing? If no, is there any better option to use?
Please do note that the chat app completely done, so I'm hoping perhaps there's a way I could directly convert the project to a Nuget package.
Thanks in anticipation!
If the host application is a Xamarin Forms one:
-Move your cross platform shared code into a PCL or .Net Standard (ContentPages, ContentViews, Classes).
-Move your Renderers and platform specific code to Android and iOs Class Libraries.
Your client will have to reference your first assembly (dll) in their XF assembly in order to instantiate/manipulate your views/classes and platform specifics one on their Back-end side (taking into account your renderers, effects, etc ...)
A lot of Xamarin Controls Libraries Open Source hosted on Github are working like that. For example this one: https://github.com/jamesmontemagno/Xamarin.Forms-PullToRefreshLayout
If the host application is a native application, take a look into Xamarin forms embedding
Finally, I seem to solve the problem by enabling visual studio to build Nuget packages for the chat app project (summing up to 3 nuget packages) on project build.
Thanks #Rudy Spano and #Micah Switzer for your contributions
I have developed a simple form which don't have any .Net requirements but the published forms is not opening in users system and showing message to install .Net framework in users systems.
But this issue is happening with Visual Studio only and if I create the same form in VB6 then the form is working nicely without any .Net installation requirement.
Any suggestion about how to get rid of this .Net installation requirement (in Users Systems) in VS forms?
Both VB6 and VB.NET have prerequisites. It just happens that VB6 is so old that the required prerequisites are already included in all operating systems still in use (Windows NT 4 SP4 and above).
You say that you "don't use any .net related things". That's not true. VB.NET itself is part of the .NET framework, as well as the UI library you use (probably WinForms).
If you need your application to run without prerequisites, you could target an earlier version of the framework: .NET 2.0 is included in Vista and above, .NET 3.5 is included in Windows 7 and above.
The System.Windows.Form object is part of .Net. So is every one of the controls you're using on your form. So, if you develop any kind of form in VS (later than VS 6) you are using the .Net framework whether you realize it or not. In this case, it isn't one of Microsoft's arbitrary requirements.
You should also realize that the VB6 Runtime module has to be installed on the target machine for the VB6 version of your form to work properly, too. So, if it runs fine, it's only because that module happens to already be registered on your target machine. That might not always be the case.
I have recently written two small apps in Visual Studio 2012 (VB). I compiled them using Framework 4.5. These have been tested on the end user's PC's and the feedback was to try and get the Apps Compiled using Framework 3.5 as this is already installed on the computers.The computers are using Windows 7.
My questions are these:
Is it possible to force a compile to use 3.5 instead of 4.5?
How would I go about doing this?
Yes, it is possible to target the 3.5 framework when you compile.
Go to PROJECT-> Properties (You can also right-click on the project in the solution viewer and select Properties).
Select .NET Framework 35. in the Target Framework dropdown.
The project will be closed and reopened automatically by Visual Studio (you will be asked to confirm this change).
Note that if you have anything specific to .NET 4.0/4.5 that is NOT present in the 3.5 framework you will have to make the necessary changes.
EDIT
A picture is worth a thousand words: