Only 14% of organizations run exclusively NoSQL databases on the backend of their big data applications. 

This video provides an Oracle Database .NET Core introduction. Learn step by step how to develop a simple ODP.NET Core application and connect to the Oracle Database.  

I’m happy to announce the release of Oracle Entity Framework Core (EF Core) 3.19.0 beta on NuGet Gallery. This beta supports the new changes in Entity Framework Core 3.1. Since it’s a beta, be sure to check off the “Include Prerelease” box when searching for the assembly on NuGet Gallery. 

The decision reached on March 27, 2018 was that:
Google’s use of the Java API packages was not fair as a matter of law. 

• صفحه‌ی اصلی
• منو
• یک صفحه‌ی خوش آمدگویی
• صفحه‌ی ورود و نمایش اطلاعات
  

<Window x:Class="TwoViews.MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        Title="MVVM Light View Switching"
        d:DesignHeight="300"
        d:DesignWidth="300"
        DataContext="{Binding Main,
                              Source={StaticResource Locator}}"
        ResizeMode="NoResize"
        SizeToContent="WidthAndHeight"
        mc:Ignorable="d">
    <Grid>
        <Grid.RowDefinitions>
            <RowDefinition Height="Auto" />
            <RowDefinition Height="Auto" />
        </Grid.RowDefinitions>

        <ContentControl Content="{Binding CurrentViewModel}" />

        <DockPanel Grid.Row="1" Margin="5">
            <Button Width="75"
                    Height="23"
                    Command="{Binding SecondViewCommand}"
                    Content="Second View"
                    DockPanel.Dock="Right" />
            <Button Width="75"
                    Height="23"
                    Command="{Binding FirstViewCommand}"
                    Content="First View"
                    DockPanel.Dock="Left" />
        </DockPanel>
    </Grid>
</Window>

    /// This is our MainViewModel that is tied to the MainWindow via the 
    /// ViewModelLocator class.
    /// </summary>
    public class MainViewModel : ViewModelBase
    {
        /// <summary>
        /// Static instance of one of the ViewModels.
        /// </summary>
        private static readonly SecondViewModel SecondViewModel = new SecondViewModel();
        /// <summary>
        /// Static instance of one of the ViewModels.
        /// </summary>
        private static readonly FirstViewModel FirstViewModel = new FirstViewModel();
        /// <summary>
        /// The current view.
        /// </summary>
        private ViewModelBase _currentViewModel;
        /// <summary>
        /// Default constructor.  We set the initial view-model to 'FirstViewModel'.
        /// We also associate the commands with their execution actions.
        /// </summary>
        public MainViewModel()
        {
            CurrentViewModel = FirstViewModel;
            FirstViewCommand = new RelayCommand(ExecuteFirstViewCommand);
            SecondViewCommand = new RelayCommand(ExecuteSecondViewCommand);
        }
        /// <summary>
        /// The CurrentView property.  The setter is private since only this 
        /// class can change the view via a command.  If the View is changed,
        /// we need to raise a property changed event (via INPC).
        /// </summary>
        public ViewModelBase CurrentViewModel
        {
            get { return _currentViewModel; }
            set
            {
                if (_currentViewModel == value)
                    return;
                _currentViewModel = value;
                RaisePropertyChanged("CurrentViewModel");
            }
        }
        /// <summary>
        /// Simple property to hold the 'FirstViewCommand' - when executed
        /// it will change the current view to the 'FirstView'
        /// </summary>
        public ICommand FirstViewCommand { get; private set; }
        /// <summary>
        /// Simple property to hold the 'SecondViewCommand' - when executed
        /// it will change the current view to the 'SecondView'
        /// </summary>
        public ICommand SecondViewCommand { get; private set; }
        /// <summary>
        /// Set the CurrentViewModel to 'FirstViewModel'
        /// </summary>
        private void ExecuteFirstViewCommand()
        {
            CurrentViewModel = FirstViewModel;
        }
        /// <summary>
        /// Set the CurrentViewModel to 'SecondViewModel'
        /// </summary>
        private void ExecuteSecondViewCommand()
        {
            CurrentViewModel = SecondViewModel;
        }
    }

    <Application.Resources>
        <vm:ViewModelLocator x:Key="Locator" d:IsDataSource="True" />
        <!--
            We define the data templates here so we can apply them across the
            entire application.
         
            The data template just says that if our data type is of a particular
            view-model type, then render the appropriate view.  The framework
            takes care of this dynamically.  Note that the DataContext for
            the underlying view is already set at this point, so the
            view (UserControl), doesn't need to have it's DataContext set
            directly.
        -->
        <DataTemplate DataType="{x:Type vm:SecondViewModel}">
            <views:SecondView />
        </DataTemplate>
        <DataTemplate DataType="{x:Type vm:FirstViewModel}">
            <views:FirstView />
        </DataTemplate>
    </Application.Resources>

• We improved solution load performance by optimizing design time build.
• We've added installation progress details on Visual Studio Installer.
• You can pause your installation and resume at a later time.
• We streamlined the update process so the notification takes you directly to the Installer.
• Non-administrators can create a VS layout.
• We added a new shortcut for Edit.Duplicate in the keyboard mapping.
• We made significant improvements to the F# language and tools, particularly for .NET Core SDK projects.
• The C++ compiler optimizes your code to run faster through improved optimizations.
• C++ Mapfile generation overhead is reduced in full linking scenarios.
• Debug options are available for Embedded ARM GCC support.
• We added strong name signing on CoreCLR for the C# compiler.
• Visual Studio Tools for Xamarin has lots of new productivity updates for iOS and Android developers.
• Python no longer requires a completion DB, and Anaconda users have support for conda.
• The Performance Profiler's CPU Usage Tool can display logical call stacks for asynchronous code.
• The CPU Usage tool displays source line highlighting and async/await code with logical 'Call Stack Stitching'.
• The debugger supports thread names set via SetThreadDescription APIs in dump debugging.
• Snapshot Debugging can be started from the Debug Target dropdown for ASP.NET applications.
• We've launched the initial implementation of Navigate to decompiled sources for .NET code navigation.
• New enhancements for Configure Continuous Delivery include support for TFVC, Git authentication over SSH, and containerized projects.
• You can now click on the Continuous Delivery tile in Team Explorer to configure automated build and deployments for your application.
• Team Explorer supports Git tags and checking out pull request branches.
• Service Fabric Tooling for the 6.1 Service Fabric release is now available.
• The Windows 10 Insider Preview SDK can be installed as an optional component.
• File versions for a number of Visual Studio executables now reflect the minor release.
• Test Explorer has a hierarchy view and real time test discovery is now on by default.
• We have added support for testing Win10 IoT Core applications.
• Visual Studio Build Tools supports TypeScript and Node.js.
• ClickOnce Tools support signing application and deployment manifests with CNG certificate.
• You can access Azure resources such as Key Vault using your Visual Studio accounts. 

IKVM is an implementation of Java for the Microsoft .NET platform. It can be used to quickly and easily:

• Execute compiled Java code (bytecode) on .NET Framework or .NET Core
• Convert bytecode to a .NET assembly to directly access its API in a .NET project